Repository navigation
[sc-208568] Move GitHub Actions off Node 20 - #47
Merged
Merged
Conversation
Bump actions/checkout v4 -> v7, actions/setup-java v4 -> v6, gradle/actions/setup-gradle v4 -> v6, timheuer/base64-to-file v1 -> v2 and peter-evans/repository-dispatch v1 -> v4. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Mallear
marked this pull request as ready for review
September 29, 2026 14:40
musketyr
approved these changes
Sep 29, 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
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 is retiring Node 20 on Actions runners, and every JavaScript action has to run on Node 24 (epic sc-208536). This PR moves every node12/node20 action used by this repo's workflows to a Node 24 release. Story: https://app.shortcut.com/agorapulse/story/208568. Audit and migration notes: https://agorapulse.slite.com/app/docs/9IsAaizelUFHVV.
Actions changed
actions/checkoutv7(node24)actions/setup-javav6(node24)gradle/actions/setup-gradlev6(node24)timheuer/base64-to-filev2(node24)peter-evans/repository-dispatchv4(node24)The repo's major-tag pinning style is kept (for example
@v7, not a SHA).Behaviour changes for reviewers
pull_request_target/workflow_run. This repo doesn't use either trigger, so it has no effect here. Since v6, persisted credentials live in a file under$RUNNER_TEMPinstead of.git/config. Nothing in this repo's release job reads the token from.git/config.gitPublishPushgets its credentials fromGIT_PUBLISH_USERNAME/GIT_PUBLISH_PASSWORD.distributionis already set everywhere, and no workflow uses thecacheinput, so the new "cache the JDK too" behaviour doesn't apply.platform-github-actions): no inputs to migrate. v6's default caching (cache-provider: enhanced) is the proprietarygradle-actions-cachingcomponent, and using it counts as accepting the Gradle Terms of Use. It's free for public repos like this one. The cache protocol changed in v6.3.0, so the first run after merge will miss the cache. v6.4.0+ also adds EOL-Gradle warning annotations.filePath) are unchanged, and dispatch still sends the sameJSON.parse(client-payload)tocreateDispatchEvent.>= v2.327.1. The GitHub-hostedubuntu-latestrunners used here meet that.Not exercised by this PR
release.ymlruns only onrelease: published. PGP decoding (base64-to-file), the Maven Central publish and the upstreamrepository-dispatchjobs are not exercised here. They will first run on the next release.gradle.yml(Check) is exercised by this PR (pushandpull_request).🤖 Generated with Claude Code