Repository navigation
CI: update GitHub actions to Node.js 24 versions (1.4-maint) - #10594
Merged
ThomasWaldmann merged 2 commits intoNov 4, 2026
Merged
Conversation
The runners force actions targeting Node.js 20 to run on Node.js 24 and warn about it. Update these actions to their current major versions, which target Node.js 24 (same majors as on master): - actions/checkout v4 -> v7 - actions/setup-python v5 -> v7 - actions/cache v4 -> v6 - actions/upload-artifact v4 -> v7 - codecov/codecov-action v4 -> v7 - github/codeql-action v2 -> v4 (v2 is deprecated and errors out) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Like on master, reference each action by its full commit SHA, with the release it corresponds to in a trailing comment. actions/attest-build-provenance is pinned to v3.0.0, which is what the floating v3 tag points to. Co-Authored-By: Claude Opus 5.5 <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.
The 1.4-maint CI runs show "Node.js 20 is deprecated" warnings: the runners force these actions onto Node.js 24. The CodeQL job also gets a failure annotation because
github/codeql-actionv2 is deprecated.This updates the affected actions to their current major versions. All of them target Node.js 24, and they are the same majors master already uses:
actions/checkoutv4 -> v7actions/setup-pythonv5 -> v7actions/cachev4 -> v6actions/upload-artifactv4 -> v7 (only used on tag builds)codecov/codecov-actionv4 -> v7 (we only passtokenandenv_vars, which are unaffected by the v5file->filesrename)github/codeql-action/{init,analyze}v2 -> v4These are already on Node.js 24 and stay unchanged:
msys2/setup-msys2@v2,actions/attest-build-provenance@v3,cross-platform-actions/action@v1.5.0,chartboost/ruff-action@v1.Not addressed here: the
cross-platform-actionswarning that theruninput is deprecated. It is unrelated to Node.js and needs the VM steps restructured.All actions are now pinned to full commit SHAs with the release in a trailing comment (e.g.
actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1), the same style and SHAs as on master.actions/attest-build-provenance(not used on master) is pinned to v3.0.0, which is what the floatingv3tag points to.🤖 Generated with Claude Code