chore(deps): update all github action dependencies #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/all-github-action
branch
4 times, most recently
from
427b7f5 to
a4e359c
Compare
renovate
bot
force-pushed
the
renovate/all-github-action
branch
4 times, most recently
from
c602a6f to
3a03fa2
Compare
renovate
bot
force-pushed
the
renovate/all-github-action
branch
3 times, most recently
from
0635cd6 to
02ba424
Compare
renovate
bot
force-pushed
the
renovate/all-github-action
branch
from
02ba424 to
27a4eaa
Compare
renovate
bot
force-pushed
the
renovate/all-github-action
branch
2 times, most recently
from
e92bc78 to
e51ae06
Compare
renovate
bot
force-pushed
the
renovate/all-github-action
branch
2 times, most recently
from
59fd1ad to
fd840e8
Compare
renovate
bot
force-pushed
the
renovate/all-github-action
branch
3 times, most recently
from
711bea2 to
677d646
Compare
renovate
bot
force-pushed
the
renovate/all-github-action
branch
2 times, most recently
from
1b08730 to
278b012
Compare
renovate
bot
force-pushed
the
renovate/all-github-action
branch
from
278b012 to
bd1abb3
Compare
renovate
bot
force-pushed
the
renovate/all-github-action
branch
from
bd1abb3 to
ef9186e
Compare
renovate
bot
force-pushed
the
renovate/all-github-action
branch
4 times, most recently
from
ef0b0ae to
dbef598
Compare
renovate
bot
force-pushed
the
renovate/all-github-action
branch
from
dbef598 to
addd073
Compare
renovate
bot
force-pushed
the
renovate/all-github-action
branch
3 times, most recently
from
8850d1c to
2569651
Compare
renovate
bot
force-pushed
the
renovate/all-github-action
branch
3 times, most recently
from
368cebc to
f791b46
Compare
renovate
bot
force-pushed
the
renovate/all-github-action
branch
from
f791b46 to
ab2b863
Compare
renovate
bot
force-pushed
the
renovate/all-github-action
branch
from
ab2b863 to
010d302
Compare
renovate
bot
force-pushed
the
renovate/all-github-action
branch
2 times, most recently
from
5bfa36e to
3b43af6
Compare
renovate
bot
force-pushed
the
renovate/all-github-action
branch
3 times, most recently
from
fd2a08e to
eb80bd6
Compare
renovate
bot
force-pushed
the
renovate/all-github-action
branch
from
eb80bd6 to
f2f79fd
Compare
renovate
bot
force-pushed
the
renovate/all-github-action
branch
from
f2f79fd to
247bc98
Compare
renovate
bot
force-pushed
the
renovate/all-github-action
branch
3 times, most recently
from
3b4859b to
3449e16
Compare
renovate
bot
force-pushed
the
renovate/all-github-action
branch
from
3449e16 to
269fa79
Compare
renovate
bot
force-pushed
the
renovate/all-github-action
branch
2 times, most recently
from
ca8bbcf to
eed20f0
Compare
renovate
bot
force-pushed
the
renovate/all-github-action
branch
2 times, most recently
from
d05e813 to
8e79d3f
Compare
renovate
bot
force-pushed
the
renovate/all-github-action
branch
2 times, most recently
from
0d3d499 to
efade85
Compare
renovate
bot
force-pushed
the
renovate/all-github-action
branch
from
efade85 to
cb577f2
Compare
renovate
bot
force-pushed
the
renovate/all-github-action
branch
2 times, most recently
from
98b7f28 to
3576485
Compare
Signed-off-by: cilium-renovate[bot] <134692979+cilium-renovate[bot]@users.noreply.github.com>
renovate
bot
force-pushed
the
renovate/all-github-action
branch
from
3576485 to
43c3ae2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v3.3.1->v3.4.3v3.5.3->v3.6.0v3.0.6->v3.0.7v2.0.3->v2.0.5v4.0.1->v4.1.0v3.7.0->v3.8.20b7f8ab->ff15f03v3.1.2->v3.2.1v3.1.3->v3.2.1v4.1.1->v4.2.1v2.8.0->v2.10.0v2.9.1->v2.10.0v2.11.1->v2.12.0v2.20.4->v2.28.1v3.6.0->v3.7.1v1.5.0->v1.12.0v1.8.0->v1.10.0v1.0.2->v1.0.4v2.8.3->v2.9.01467290v2.8.3->v2.9.0v39.0.1->v39.2.4Release Notes
actions/cache (actions/cache)
v3.4.3Compare Source
v3.4.2Compare Source
What's Changed
Full Changelog: actions/cache@v3.4.0...v3.4.2
v3.4.1Compare Source
v3.4.0Compare Source
The cache backend service has been rewritten from the ground up for improved performance and reliability. actions/cache now integrates with the new cache service (v2) APIs.
The new service will gradually roll out as of February 1st, 2025. The legacy service will also be sunset on the same date. Changes in these release are fully backward compatible.
We are deprecating some versions of this action. We recommend upgrading to version
v4orv3as soon as possible before February 1st, 2025. (Upgrade instructions below).If you are using pinned SHAs, please use the SHAs of versions
v4.2.0orv3.4.0If you do not upgrade, all workflow runs using any of the deprecated actions/cache will fail.
Upgrading to the recommended versions will not break your workflows.
Read more about the change & access the migration guide: reference to the announcement.
Minor changes
Minor and patch version updates for these dependencies:
1.11.11.1.30.38.3Full Changelog: actions/cache@v3.3.3...v3.4.0
v3.3.3Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v3.3.3
v3.3.2Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v3.3.2
actions/checkout (actions/checkout)
v3.6.0Compare Source
actions/configure-pages (actions/configure-pages)
v3.0.7Compare Source
Changelog
See details of all code changes since previous release.
actions/deploy-pages (actions/deploy-pages)
v2.0.5Compare Source
Changelog
See details of all code changes since previous release.
v2.0.4Compare Source
Changelog
3.9.x@JamesMGreene (#201)See details of all code changes since previous release.
actions/setup-go (actions/setup-go)
v4.1.0Compare Source
What's Changed
In scope of this release, slow installation on Windows was fixed by @dsame in https://github.com/actions/setup-go/pull/393 and OS version was added to
primaryKeyfor Ubuntu runners to avoid conflicts (https://github.com/actions/setup-go/pull/383)This release also includes the following changes:
New Contributors
Full Changelog: actions/setup-go@v4...v4.1.0
actions/setup-node (actions/setup-node)
v3.8.2Compare Source
What's Changed
Full Changelog: actions/setup-node@v3...v3.8.2
v3.8.1Compare Source
What's Changed
In scope of this release, the filter was removed within the cache-save step by @dmitry-shibanov in https://github.com/actions/setup-node/pull/831. It is filtered and checked in the toolkit/cache library.
Full Changelog: actions/setup-node@v3...v3.8.1
v3.8.0Compare Source
What's Changed
Bug fixes:
Feature implementations:
Documentation changes:
Update dependencies:
New Contributors
Full Changelog: actions/setup-node@v3...v3.8.0
actions/upload-artifact (actions/upload-artifact)
v3.2.1Compare Source
What's Changed
This fixes the
include-hidden-filesinput introduced in https://github.com/actions/upload-artifact/releases/tag/v3.2.0Full Changelog: actions/upload-artifact@v3.2.0...v3.2.1
v3.2.0Compare Source
Notice: Breaking Changes⚠️
We will no longer include hidden files and folders by default in the
upload-artifactaction of this version. This reduces the risk that credentials are accidentally uploaded into artifacts. Customers who need to continue to upload these files can use a new option,include-hidden-files, to continue to do so.See "Notice of upcoming deprecations and breaking changes in GitHub Actions runners" changelog and this issue for more details.
What's Changed
Full Changelog: actions/upload-artifact@v3.1.3...v3.2.0
v3.1.3Compare Source
What's Changed
Full Changelog: actions/upload-artifact@v3...v3.1.3
docker/build-push-action (docker/build-push-action)
v4.2.1Compare Source
Full Changelog: docker/build-push-action@v4.2.0...v4.2.1
v4.2.0Compare Source
Full Changelog: docker/build-push-action@v4.1.1...v4.2.0
docker/setup-buildx-action (docker/setup-buildx-action)
v2.10.0Compare Source
Full Changelog: docker/setup-buildx-action@v2.9.1...v2.10.0
v2.9.1Compare Source
Full Changelog: docker/setup-buildx-action@v2.9.0...v2.9.1
v2.9.0Compare Source
Full Changelog: docker/setup-buildx-action@v2.8.0...v2.9.0
dorny/paths-filter (dorny/paths-filter)
v2.12.0Compare Source
github/codeql-action (github/codeql-action)
v2.28.1Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
This is the last planned release of the
v2. To continue getting updates for the CodeQL Action, please switch tov3.2.28.1 - 10 Jan 2025
See the full CHANGELOG.md for more information.
v2.28.0Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2andv3of the CodeQL Action is the node version they support, withv3running on node 20 while we continue to releasev2to support running on node 16. For example3.22.11was the firstv3release and is functionally identical to2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.This is the last planned release of the
v2. To continue getting updates for the CodeQL Action, please switch tov3.2.28.0 - 20 Dec 2024
See the full CHANGELOG.md for more information.
v2.27.9Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2andv3of the CodeQL Action is the node version they support, withv3running on node 20 while we continue to releasev2to support running on node 16. For example3.22.11was the firstv3release and is functionally identical to2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.2.27.9 - 12 Dec 2024
No user facing changes.
See the full CHANGELOG.md for more information.
v2.27.8Compare Source
v2.27.7Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2andv3of the CodeQL Action is the node version they support, withv3running on node 20 while we continue to releasev2to support running on node 16. For example3.22.11was the firstv3release and is functionally identical to2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.2.27.7 - 10 Dec 2024
See the full CHANGELOG.md for more information.
v2.27.6Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2andv3of the CodeQL Action is the node version they support, withv3running on node 20 while we continue to releasev2to support running on node 16. For example3.22.11was the firstv3release and is functionally identical to2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.2.27.6 - 03 Dec 2024
See the full CHANGELOG.md for more information.
v2.27.5Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2andv3of the CodeQL Action is the node version they support, withv3running on node 20 while we continue to releasev2to support running on node 16. For example3.22.11was the firstv3release and is functionally identical to2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.2.27.5 - 19 Nov 2024
No user facing changes.
See the full CHANGELOG.md for more information.
v2.27.4Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2andv3of the CodeQL Action is the node version they support, withv3running on node 20 while we continue to releasev2to support running on node 16. For example3.22.11was the firstv3release and is functionally identical to2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.2.27.4 - 14 Nov 2024
No user facing changes.
See the full CHANGELOG.md for more information.
v2.27.3Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2andv3of the CodeQL Action is the node version they support, withv3running on node 20 while we continue to releasev2to support running on node 16. For example3.22.11was the firstv3release and is functionally identical to2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.2.27.3 - 12 Nov 2024
No user facing changes.
See the full CHANGELOG.md for more information.
v2.27.2Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2andv3of the CodeQL Action is the node version they support, withv3running on node 20 while we continue to releasev2to support running on node 16. For example3.22.11was the firstv3release and is functionally identical to2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.2.27.2 - 12 Nov 2024
See the full CHANGELOG.md for more information.
v2.27.1Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2andv3of the CodeQL Action is the node version they support, withv3running on node 20 while we continue to releasev2to support running on node 16. For example3.22.11was the firstv3release and is functionally identical to2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.2.27.1 - 08 Nov 2024
See the full CHANGELOG.md for more information.
v2.27.0Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2andv3of the CodeQL Action is the node version they support, withv3running on node 20 while we continue to releasev2to support running on node 16. For example3.22.11was the firstv3release and is functionally identical to2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.2.27.0 - 22 Oct 2024
upload-sarifAction would fail with "upload-sarif post-action step failed: Input required and not supplied: token" when called in a composite Action that had a different set of inputs to the ones expected by theupload-sarifAction. #2557See the full CHANGELOG.md for more information.
v2.26.13Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2andv3of the CodeQL Action is the node version they support, withv3running on node 20 while we continue to releasev2to support running on node 16. For example3.22.11was the firstv3release and is functionally identical to2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.2.26.13 - 14 Oct 2024
No user facing changes.
See the full CHANGELOG.md for more information.
v2.26.12Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2andv3of the CodeQL Action is the node version they support, withv3running on node 20 while we continue to releasev2to support running on node 16. For example3.22.11was the firstv3release and is functionally identical to2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.2.26.12 - 07 Oct 2024
github/codeql-action/*@​v3bygithub/codeql-action/*@​v3.26.11andgithub/codeql-action/*@​v2bygithub/codeql-action/*@​v2.26.11in your code scanning workflow to ensure you continue using this version of the CodeQL Action.See the full CHANGELOG.md for more information.
v2.26.11Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2andv3of the CodeQL Action is the node version they support, withv3running on node 20 while we continue to releasev2to support running on node 16. For example3.22.11was the firstv3release and is functionally identical to2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.2.26.11 - 03 Oct 2024
actions/download-artifact@v4to programmatically consume CodeQL Action debug artifacts.Starting November 30, 2024, github.com customers will no longer be able to use
actions/download-artifact@v3. Therefore, to avoid breakage, customers who programmatically download the CodeQL Action debug artifacts should set theCODEQL_ACTION_ARTIFACT_V4_UPGRADEenvironment variable totrueand bumpactions/download-artifact@v3toactions/download-artifact@v4in their workflows. The CodeQL Action will enable this behavior by default in early November and workflows that have not yet bumped toactions/download-artifact@v3toactions/download-artifact@v4will begin failing then.This change is currently unavailable for GitHub Enterprise Server customers, as
actions/upload-artifact@v4andactions/download-artifact@v4are not yet compatible with GHES.See the full CHANGELOG.md for more information.
v2.26.10Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2andv3of the CodeQL Action is the node version they support, withv3running on node 20 while we continue to releasev2to support running on node 16. For example3.22.11was the firstv3release and is functionally identical to2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.2.26.10 - 30 Sep 2024
See the full CHANGELOG.md for more information.
v2.26.9Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2andv3of the CodeQL Action is the node version they support, withv3running on node 20 while we continue to releasev2to support running on node 16. For example3.22.11was the firstv3release and is functionally identical to2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.2.26.9 - 24 Sep 2024
No user facing changes.
See the full CHANGELOG.md for more information.
v2.26.8Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2andv3of the CodeQL Action is the node version they support, withv3running on node 20 while we continue to releasev2to support running on node 16. For example3.22.11was the firstv3release and is functionally identical to2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.2.26.8 - 19 Sep 2024
See the full CHANGELOG.md for more information.
v2.26.7Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2andv3of the CodeQL Action is the node version they support, withv3running on node 20 while we continue to releasev2to support running on node 16. For example3.22.11was the firstv3release and is functionally identical to2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.2.26.7 - 13 Sep 2024
See the full CHANGELOG.md for more information.
v2.26.6Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2andv3of the CodeQL Action is the node version they support, withv3running on node 20 while we continue to releasev2to support running on node 16. For example3.22.11was the firstv3release and is functionally identical to2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.2.26.6 - 29 Aug 2024
See the full CHANGELOG.md for more information.
v2.26.5Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2andv3of the CodeQL Action is the node version they support, withv3running on node 20 while we continue to releasev2to support running on node 16. For example3.22.11was the firstv3release and is functionally identical to2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.2.26.5 - 23 Aug 2024
csrutilsystem call used for telemetry would fail on MacOS ARM machines with System Integrity Protection disabled. #2441See the full CHANGELOG.md for more information.
v2.26.4Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2andv3of the CodeQL Action is the node version they support, withv3running on node 20 while we continue to releasev2to support running on node 16. For example3.22.11was the firstv3release and is functionally identical to2.22.11. This approach ensures an easy way to track exactlConfiguration
📅 Schedule: Branch creation - "every month" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.