ci: bump GitHub Actions to Node 24 runtimes#172
Merged
Conversation
GitHub forces Node.js 20 actions to run on Node 24 from June 16th 2026 and removes Node 20 from runners in September 2026. Bump all pinned actions to their current majors, which run on node24 natively: - actions/checkout v4 -> v6 (credential persistence change is irrelevant here; no workflow pushes via git after checkout) - actions/setup-python v5 -> v6 - actions/upload-artifact v4 -> v7 - actions/download-artifact v4 -> v8 (both usages download by name with an explicit path, so the v5 by-id path change and v8 direct-download behavior do not apply) - actions/setup-node v4 -> v6 - actions/github-script v7 -> v9 (script only uses the injected github/context objects, unaffected by the ESM breaking changes) - actions/cache v3 -> v5 - cloudflare/wrangler-action v3 -> v4 (default wrangler version change does not apply; both usages pin wranglerVersion explicitly) Swatinem/rust-cache@v2 and rust-lang/crates-io-auth-action@v1 already resolve to node24 releases on their floating major tags, and dtolnay/rust-toolchain is a composite action.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
📖 Documentation Preview: https://reflectapi-docs-preview-pr-172.partly.workers.dev Updated automatically from commit b8cef14 |
This was referenced Jun 11, 2026
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.
GitHub forces Node.js 20 actions to run on Node 24 starting June 16th, 2026 (five days away) and removes Node 20 from runners in September 2026 — the v0.17.6 release run was already emitting deprecation warnings for
checkout,setup-python,upload-artifact, anddownload-artifact.This bumps every pinned action to its current major, all of which run
node24natively (verified against each action'saction.yml):actions/checkoutgit pushafter checkoutactions/setup-pythonactions/upload-artifactarchiveinput unused; ESM change is internalactions/download-artifactpath:actions/setup-nodepackageManagerfield in package.json; none at repo rootactions/github-scriptrequire('@actions/github')— our script only uses the injectedgithub/contextobjectsactions/cachecloudflare/wrangler-actionwranglerVersion: "4.32.0"Left as-is:
Swatinem/rust-cache@v2andrust-lang/crates-io-auth-action@v1(floating major tags already resolve to node24 releases),dtolnay/rust-toolchain(composite action, no Node runtime),pypa/gh-action-pypi-publish@release/v1(docker action).Note: this PR's CI exercises
ci.yamland the docs workflows (including the github-script PR comment), butrelease.ymlonly runs on tags — it gets its first real validation on the next release.