ci: update GitHub Actions to Node 24 runtime & drop battila7/get-version-action - #326
Open
BWibo wants to merge 2 commits into
Open
ci: update GitHub Actions to Node 24 runtime & drop battila7/get-version-action#326BWibo wants to merge 2 commits into
BWibo wants to merge 2 commits into
Conversation
GitHub Actions runners now default to Node.js 24 and are removing the Node.js 20 runtime. Bump all actions that still declare node20 (or older) to their Node 24 native major versions to clear the deprecation warnings: - actions/checkout v4 -> v5 - actions/setup-java v3 -> v5 - docker/login-action v3 -> v4 - docker/build-push-action v6 -> v7 - benjlevesque/short-sha v3.0 -> v4.0 Also migrate the deprecated gradle/gradle-build-action@v2 (node16) to gradle/actions/setup-gradle@v5; the cache-disabled input is preserved and the build still runs via a separate ./gradlew step.
battila7/get-version-action@v2 declares the ancient node12 runtime and internally uses the deprecated `set-output` workflow command, so it emits both the Node.js and set-output deprecation warnings. Replace it in both release workflows with a small POSIX shell step that derives the version from the release tag and writes to $GITHUB_OUTPUT, preserving the existing `version` and `version-without-v` outputs so downstream references are unchanged.
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.
Why
GitHub Actions runners now default to Node.js 24 (since 2026-06-16) and the Node.js 20 runtime is being removed (2026-09-16). Several actions in our workflows still declare
node20(or older) in theiraction.yml, so the pipelines emit the Node.js 20 deprecation warning.battila7/get-version-action@v2additionally declares the ancient node12 runtime and internally uses the deprecatedset-outputcommand, so it triggers both the Node.js andset-outputdeprecation warnings.gradle/gradle-build-action@v2is a deprecated action (node16) superseded bygradle/actions/setup-gradle.What
Commit 1 — bump actions to Node 24 native versions (verified against each target tag's
action.ymlruns.using: node24):The gradle migration is a drop-in: the
cache-disabledinput is preserved and the build still runs via the separate./gradlew buildstep.Commit 2 — replace
battila7/get-version-actionin both release workflows with a POSIX shell step that derives the version from the release tag and writes to$GITHUB_OUTPUT.version/version-without-voutputs are preserved, so downstream references are unchanged. This clears theset-outputdeprecation.Validation
actionlintclean.v1.2.3/1.2.3tag forms.impexp-build(push/PR) exercises the checkout / setup-java / setup-gradle bumps live in this PR.