Bump GitHub Actions to Node 24-compatible major versions - #661
Merged
Conversation
Every CI run prints "Node.js 20 is deprecated" warnings for actions still declaring runs.using: node20 in their action.yml, which GitHub now force-runs on Node 24 anyway. Same issue previously seen and fixed in the RSE_course_JuRSE project. Verified each action's actual runs.using value at both the currently-pinned and candidate new major version before bumping, rather than assuming from version numbers alone: - actions/checkout: v1 (lint job only - a legacy pre-Node "plugin" action, not itself the source of the node20 warning, but badly outdated) and v4 (node20) -> v7 (node24) - actions/upload-artifact: v4 (node20) -> v7 (node24) - actions/download-artifact: v4 (node20) -> v8 (node24) - mamba-org/setup-micromamba: v1 (node20) -> v3 (node24); confirmed the two inputs actually used here (environment-file, create-args) are unchanged in v3 Left alone (confirmed not implicated in the warning at all): - codecov/codecov-action@v5 - composite action, no Node runtime - py-cov-action/python-coverage-comment-action@v3 - Docker action, no Node runtime - JamesIves/github-pages-deploy-action@v4 - already node24 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2 tasks
Coverage report
This PR does not seem to contain any modification to coverable code. |
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
Every CI run prints "Node.js 20 is deprecated" warnings for actions still declaring
runs.using: node20in theiraction.yml, which GitHub now force-runs on Node 24 anyway. Same issue previously seen and fixed in the RSE_course_JuRSE project.(Supersedes #660, which was accidentally built on the already-merged #659 branch and dragged its full commit history along even though the file diff was identical. This PR is the same change on a clean branch off current
master.)Verified each action's actual
runs.usingvalue at both the currently-pinned and candidate new major version before bumping, not just assumed from version numbers:actions/checkout:v1(lint job only — a legacy pre-Node "plugin" action, not itself the source of the node20 warning, but badly outdated) andv4(node20) →v7(node24)actions/upload-artifact:v4(node20) →v7(node24)actions/download-artifact:v4(node20) →v8(node24)mamba-org/setup-micromamba:v1(node20) →v3(node24) — confirmed the two inputs actually used here (environment-file,create-args) are unchanged inv3Left alone (confirmed not implicated in the warning at all):
codecov/codecov-action@v5— composite action, no Node runtimepy-cov-action/python-coverage-comment-action@v3— Docker action, no Node runtimeJamesIves/github-pages-deploy-action@v4— alreadynode24Test plan
🤖 Generated with Claude Code