Update GitHub Actions (release/v0.5) (major) - abandoned#859
Closed
renovate-rancher[bot] wants to merge 1 commit into
Closed
Update GitHub Actions (release/v0.5) (major) - abandoned#859renovate-rancher[bot] wants to merge 1 commit into
renovate-rancher[bot] wants to merge 1 commit into
Conversation
0e9694e to
060bc23
Compare
ac77577 to
2e7bb04
Compare
2e7bb04 to
0fcf52e
Compare
0fcf52e to
bb7316c
Compare
bb7316c to
9673000
Compare
9673000 to
62f1e6a
Compare
2b2bdd4 to
f722615
Compare
f722615 to
1cb4227
Compare
0bab569 to
6f41287
Compare
6f41287 to
e7dc4a1
Compare
4dc3a27 to
84b54db
Compare
84b54db to
4212194
Compare
Contributor
Author
Autoclosing SkippedThis PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error. |
Collaborator
|
Closing: this Renovate PR has been marked abandoned and is no longer relevant. |
This file contains hidden or 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
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:
v4.3.0→v6.0.2v4→v6v1→v2v4.3.0→v7.0.0v8.0.0v5.5.0→v6.2.0v6.3.0v4.6.2→v6.0.0v7.0.0Release Notes
actions/checkout (actions/checkout)
v6.0.2Compare Source
v6.0.1Compare Source
v6.0.0Compare Source
v5.0.1Compare Source
v5.0.0Compare Source
v4.3.1Compare Source
actions/create-github-app-token (actions/create-github-app-token)
v2Compare Source
actions/download-artifact (actions/download-artifact)
v7.0.0Compare Source
v7 - What's new
Node.js 24
This release updates the runtime to Node.js 24. v6 had preliminary support for Node 24, however this action was by default still running on Node.js 20. Now this action by default will run on Node.js 24.
What's Changed
New Contributors
Full Changelog: actions/download-artifact@v6.0.0...v7.0.0
v6.0.0Compare Source
What's Changed
BREAKING CHANGE: this update supports Node
v24.x. This is not a breaking change per-se but we're treating it as such.@actions/artifacttov4.0.0v6.0.0by @danwkennedy in #438New Contributors
Full Changelog: actions/download-artifact@v5...v6.0.0
v5.0.0Compare Source
What's Changed
v5.0.0
🚨 Breaking Change
This release fixes an inconsistency in path behavior for single artifact downloads by ID. If you're downloading single artifacts by ID, the output path may change.
What Changed
Previously, single artifact downloads behaved differently depending on how you specified the artifact:
name: my-artifact→ extracted topath/(direct)artifact-ids: 12345→ extracted topath/my-artifact/(nested)Now both methods are consistent:
name: my-artifact→ extracted topath/(unchanged)artifact-ids: 12345→ extracted topath/(fixed - now direct)Migration Guide
✅ No Action Needed If:
merge-multiple: trueas a workaroundYou download single artifacts by ID and your workflows expect the nested directory structure.
Before v5 (nested structure):
To maintain old behavior (if needed):
New Contributors
Full Changelog: actions/download-artifact@v4...v5.0.0
actions/setup-go (actions/setup-go)
v6.2.0Compare Source
What's Changed
Enhancements
Dependency updates
New Contributors
Full Changelog: actions/setup-go@v6...v6.2.0
v6.1.0Compare Source
What's Changed
Enhancements
Dependency updates
New Contributors
Full Changelog: actions/setup-go@v6...v6.1.0
v6.0.0Compare Source
What's Changed
Breaking Changes
Make sure your runner is on version v2.327.1 or later to ensure compatibility with this release. See Release Notes
Dependency Upgrades
form-datato bring in fix for critical vulnerability by @matthewhughes934 in #618New Contributors
Full Changelog: actions/setup-go@v5...v6.0.0
v5.6.0Compare Source
What's Changed
Full Changelog: actions/setup-go@v5...v5.6.0
actions/upload-artifact (actions/upload-artifact)
v6.0.0Compare Source
v6 - What's new
Node.js 24
This release updates the runtime to Node.js 24. v5 had preliminary support for Node.js 24, however this action was by default still running on Node.js 20. Now this action by default will run on Node.js 24.
What's Changed
Full Changelog: actions/upload-artifact@v5.0.0...v6.0.0
v5.0.0Compare Source
What's Changed
BREAKING CHANGE: this update supports Node
v24.x. This is not a breaking change per-se but we're treating it as such.@actions/artifacttov4.0.0v5.0.0by @danwkennedy in #734New Contributors
Full Changelog: actions/upload-artifact@v4...v5.0.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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 has been generated by Renovate Bot.