ci: pin actions to Node 24 majors ahead of 2026-06-16 deprecation#189
Merged
Conversation
GitHub deprecates Node.js 20 actions on 2026-06-16. Bump actions/checkout@v4 -> @v6 (Node 24 since v5.0.0), actions/setup-node@v4 -> @v6 (Node 24 since v5.0.0; v6 limits automatic caching to npm, which is the cache we already use), and actions/cache@v4 -> @v5 (Node 24 since v5.0.0). setup-node was not flagged in the original issue but uses the same Node 20 runtime at @v4; bundling it here avoids a follow-up. Closes #173
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.
Summary
GitHub deprecates Node.js 20 actions on 2026-06-16 (per the changelog). All three JavaScript actions used by
.github/workflows/ci.ymlcurrently resolve to Node 20 at@v4. Bumping each to its first Node 24 major:actions/checkout@v4->@v6(Node 24 sincev5.0.0, 2025-08-11)actions/setup-node@v4->@v6(Node 24 sincev5.0.0, 2025-09-04;v6limits automatic caching to npm, which is already what we use)actions/cache@v4->@v5(Node 24 sincev5.0.0, 2025-12-11)Note on scope
Issue #173 named only
checkoutandcache—setup-node@v4was overlooked but is on the same Node 20 runtime and the same deadline. Bundled here rather than carved into a follow-up. Verified via each action'saction.ymlat@v4(all three declareusing: 'node20').This goes with Option 3 from the issue (pin to newer majors); Options 1 (wait) and 2 (
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true) are unnecessary now that v5/v6 majors are out and stable.Test plan
Closes #173