General: Bump CI actions off the deprecated Node 20 runtime - #34
Merged
Conversation
GitHub is deprecating the Node 20 runtime and already force-runs these two actions on Node 24, emitting a warning on every job that uses the common-setup composite. - android-actions/setup-android v3.2.2 -> v4.0.1 (v4.0.0 was the Node 24 migration). Inputs are unchanged and we pass none; the only behavioral change is the default cmdline-tools version moving 11076708 -> 14742923 (20.0), which matches what recent AGP/compileSdk needs anyway. - gradle/actions/wrapper-validation v4.4.4 -> v6.2.0 (Node 24 since v5). Inputs are unchanged and we pass none. v6 split caching into the proprietary gradle-actions-caching component, but wrapper-validation is part of the MIT action runner and its dist bundle never loads it; this repo caches via actions/setup-java's `cache: gradle`, not setup-gradle. No other action in the repo targets Node 20.
github-actions
Bot
added
Build/Deploy
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 changed
No user-facing behavior change. CI-only: two GitHub Actions in the shared
common-setupcomposite are re-pinned to releases that run natively on Node 24, clearing the deprecation warning GitHub emits on every job that uses them.Technical Context
GitHub is deprecating the Node 20 runtime and currently force-runs these two actions on Node 24, warning on each job:
android-actions/setup-androidv3.2.2 → v4.0.1. v4.0.0 was the Node 24 migration. Inputs are unchanged and the composite passes none, so the only behavioral delta is the defaultcmdline-tools-versionmoving11076708→14742923(20.0) — the version recent AGP/compileSdk wants anyway. If the SDK install ever regresses, pinningcmdline-tools-version: 11076708restores the old behavior.gradle/actions/wrapper-validationv4.4.4 → v6.2.0. Node 24 since v5; inputs (min-wrapper-count/allow-snapshots/allow-checksums) are identical and we pass none.On the v6 licensing question: v6 extracted caching into the proprietary
gradle-actions-cachingcomponent. That does not apply here —wrapper-validationis part of the MIT-licensed action runner, itsdist/wrapper-validationbundle is standalone and never loads the caching library, and this repo gets its Gradle cache fromactions/setup-java'scache: gradlerather thansetup-gradle.No other action in the repo targets Node 20 (checked every
uses:across.github/workflowsand.github/actions).Review guidance: the real verification is CI itself — the warning should be gone from the jobs that use
common-setup, and the Android SDK setup should still succeed on the newer cmdline-tools default.