ci: bump checkout and setup-python to Node 24-native majors - #6
Merged
Conversation
GitHub Actions now force-runs Node 20 actions on Node 24 and is deprecating the Node 20 runtime (removal slated for late 2026). The pinned actions/checkout@v4 and actions/setup-python@v5 still declare the Node 20 runtime, producing deprecation warnings in CI. Bump to the current stable majors that run natively on Node 24: - actions/checkout v4 -> v7 - actions/setup-python v5 -> v6 checkout v7's only behavioral change vs v5/v6 (blocking fork checkouts for pull_request_target / workflow_run events) does not apply here; our workflows use plain pull_request, push, and tag triggers. The remaining third-party action, pypa/gh-action-pypi-publish@release/v1, is a composite action on a floating ref maintained upstream and is unaffected. CI maintenance only; no application code changes. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
sherryzyh
force-pushed
the
ci/bump-actions-node24
branch
from
June 22, 2026 01:31
f19f283 to
4142a15
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.
What
Bump the pinned GitHub-maintained actions in both workflows to their current stable majors, which run natively on Node.js 24:
actions/checkoutv4v7actions/setup-pythonv5v6Applied identically in
.github/workflows/ci.ymland.github/workflows/release.yml.Why
GitHub Actions now force-runs Node 20 JavaScript actions on Node 24 and is deprecating the Node 20 runtime (removal slated for late 2026).
checkout@v4andsetup-python@v5still declare the Node 20 runtime, which surfaced as a deprecation warning in CI (run27923556616).Verification
Latest stable majors confirmed on the GitHub marketplace:
actions/checkout— current major is v7 (v5/v6/v7 all run on Node 24). v7's only behavioral change vs. v5/v6 is blocking fork checkouts forpull_request_target/workflow_runevents; this does not affect us — our triggers are plainpull_request,push, and tag pushes. v6's credential-file persistence requires a recent runner, which GitHub-hostedubuntu-latestsatisfies.actions/setup-python— current major is v6 (Node 24).Other actions checked
pypa/gh-action-pypi-publish@release/v1(release workflow) is a composite action on a floating upstream-maintained ref, not a Node 20 action — left unchanged.CI maintenance only; no application code changes.
🤖 Generated with Claude Code