chore(ci): bump GitHub Actions to Node-24-compatible majors#5
Merged
Conversation
GitHub is removing Node 20 from runners on 2026-09-16 and flipping the default to Node 24 on 2026-06-02. Latest majors of every action we use now ship with `using: node24`, so upgrade them all at once: - actions/checkout v4 -> v6 - actions/setup-node v4 -> v6 - actions/configure-pages v5 -> v6 - actions/cache v4 -> v5 - actions/upload-pages-artifact v3 -> v5 - actions/setup-python v5 -> v6 actions/deploy-pages was already on v5 (latest major, node24). Ref: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
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.
Summary
GitHub is deprecating Node 20 on Actions runners:
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24flips totrueby defaultEvery action we use has a newer major that ships with
using: node24. Bumping all of them at once:actions/checkoutactions/setup-nodeactions/configure-pagesactions/cacheactions/upload-pages-artifactactions/setup-pythonactions/deploy-pagesVerified each pinned major by reading its
action.yml— all declareusing: node24(orcompositefor upload-pages-artifact, which is fine).No
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24stopgap needed since the bumped majors already run on Node 24.Test plan
Deploy Next.js site to Pagesworkflow is green on the PR branch (requires merge, since it only runs on pushes tomain)Integration testsworkflow is green — will be triggered automatically by the Deploy workflow, or can be dispatched manually againstchore/bump-gha-node24Fetch klines dailyrun completes without deprecation warnings