ci: bump GH Actions to Node 24 runtimes - #23
Merged
Conversation
GitHub deprecated the Node 20 runtime on 2025-09-19; runners have been
force-shimming Node 20 actions onto Node 24, emitting the "Node.js 20 is
deprecated" warning at the top of every job. Bumps target the highest
major of each action that actually flips `runs.using: node24` (v5 was
a false floor for upload/download-artifact — those v5 releases still
declared `runs.using: node20` and only added preliminary Node 24
support in-code).
actions/checkout v4 -> v7
actions/setup-java v4 -> v5 (already latest major)
actions/cache v4 -> v6
actions/upload-artifact v4 -> v7 (v5/v6 were preliminary;
v6 flipped the default
runtime, v7 adds opt-in
`archive: false`)
actions/download-artifact v4 -> v8 (v5/v6 preliminary; v7
flipped the default
runtime, v8 is ESM +
stricter hash-mismatch
defaults, applied only to
`name:`-keyed downloads
which is what we use)
gradle/actions/setup-gradle v4 -> v5 (pinned; v6 relicensed
the caching component to
Gradle Terms of Use)
softprops/action-gh-release v2 -> v3
Unchanged: actions/attest-build-provenance@v4 already ships on Node 24
reactivecircus/android-emulator-runner@v2, docker/* not in the warning
Co-authored-by: Cursor <cursoragent@cursor.com>
Azyyyyyy
force-pushed
the
ci-bump-node20-actions
branch
from
July 30, 2026 12:31
ef24609 to
a162ffc
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
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.
Clears the
Node.js 20 is deprecatedwarning that fires at the top of every job in run 30537101455 and run 30537104274. GitHub started force-shimming Node-20 actions onto Node 24 after the 2025-09-19 deprecation; each action below has a newer major that shipsruns.using: node24natively, so the shim message goes away for good.Bumps
Every action is bumped to the highest published major that actually flips
runs.using: node24, apart fromgradle/actions/setup-gradlewhich is deliberately held at v5 (v6 relicensed the caching component to Gradle's Terms of Use).actions/checkoutpull_request_target/workflow_run(we don't use those triggers).actions/setup-javaactions/cacheactions/upload-artifactruns.using: node20. v6 flipped the default tonode24; v7 adds an opt-inarchive: falsefor single files that we don't use.actions/download-artifactname:-keyed downloads (what we use), so the v5 single-artifact-by-ID path fix is inapplicable.gradle/actions/setup-gradlegradle-actions-cachinglibrary and using it implicitly accepts Gradle's Terms of Use per the v6 blog post.softprops/action-gh-releasev2is now a Node 20-only line.Unchanged
actions/attest-build-provenance@v4— the v4 line already ships on Node 24.reactivecircus/android-emulator-runner@v2anddocker/*— never in the deprecation warning.Verification
workflow_dispatchon this branch (publish: false) to confirm themacos-26iOS job and Android job come out clean too.