chore(ci): update actions/checkout to v6 and actions/cache to v5#209
Merged
Conversation
GSTJ
force-pushed
the
chore/bump-github-actions
branch
from
July 25, 2026 20:49
a59e922 to
a132810
Compare
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
1 participant
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.
Renovate had these as #200 and #199 and then autoclosed both without merging, so main is still on v4 everywhere. Same diff, reapplied by hand.
Both majors are just the Node 24 runtime move, which is the thing every run has been warning about ("Node.js 20 actions are deprecated... forced to Node.js 24 by default starting June 2nd, 2026"). No input or behaviour changes on our side.
Only the version tags move. Worth watching the first e2e run since it's the heaviest cache user, but restore/save keys are untouched.