Bump the Node-based GitHub Actions off Node 20#105
Merged
Conversation
GitHub is removing the Node 20 runtime; actions/checkout@v4 and actions/cache@v4 run on it and emit a deprecation warning in the logs. Bump both to v5, which run on Node 24. shivammathur/setup-php stays on its current rolling major (v2), which already runs on Node 24 and was not flagged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Why
GitHub Actions is removing the Node.js 20 runtime (JavaScript actions are forced to Node 24 from mid-June 2026, and Node 20 is removed in September 2026).
actions/checkout@v4andactions/cache@v4run on Node 20 and emit the deprecation warning seen in the CI logs.What
Bump both to v5, which run on Node 24:
actions/checkout@v4->@v5(x2)actions/cache@v4->@v5(x2)shivammathur/setup-php@v2is left as-is: v2 is its current rolling major, already runs on Node 24, and was not among the flagged actions.No workflow behaviour changes; this only moves the actions onto the supported runtime so the logs are warning-free.