Repository navigation
ci: bump GitHub Actions to Node 24 majors (checkout v7, setup-java v6, upload-artifact v7, gh-release v3) - #5
Merged
Conversation
checkout v4 -> v7, setup-java v4 -> v6, upload-artifact v4 -> v7 and softprops/action-gh-release v2 -> v3. CI flagged the old majors as Node.js 20 based and deprecated; setup-java v4 additionally no longer receives updates. Every input these workflows use still exists in the new majors (verified against each action.yml): java-version/distribution/cache, name/path/if-no-files-found/retention-days, and tag_name/name/draft/prerelease/generate_release_notes/ fail_on_unmatched_files/files. checkout is used with no inputs. Co-authored-by: arena-agent <297053741+arena-agent@users.noreply.github.com>
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 does this change?
Bumps the GitHub Actions versions used by all three workflows to their current Node.js 24 majors. Follow-up to #4, whose CI run flagged the old ones.
actions/checkoutactions/setup-javaactions/upload-artifactsoftprops/action-gh-releaseWhy?
The CI run on #4 produced these annotations:
softprops/action-gh-release@v2was not flagged only becauserelease.ymldid not run on that PR — itsaction.ymlstill saysusing: "node20", so it would warn the first time a tag is pushed. Bumping it now avoids that surprise during an actual release.How did you verify it?
action.ymlfromapi.github.comand confirmed every input these workflows use still exists:java-version/distribution/cache(setup-java v6, line 97),name/path/if-no-files-found/retention-days(upload-artifact v7),tag_name/name/draft/prerelease/generate_release_notes/fail_on_unmatched_files/files(action-gh-release v3).checkoutis used with no inputs in all three workflows, so v7 is a drop-in.using: node24.runoruses.checkout,setup-java(with the Gradle cache) and bothupload-artifactcalls.action-gh-releaseonly runs fromrelease.ymlon a tag, so it is verified by input compatibility, not by execution.Checklist
CHANGELOG.md— CI-only change, no user-visible effect; not addeddocs/CI_RELEASE.mddescribes the workflows by purpose, not by action versionNotes for the reviewer
If you would rather stay on majors that have been in production longer,
checkout@v5/setup-java@v5/upload-artifact@v5are the versions the deprecation notice itself recommended; I went to the latest majors because the runner is already forcing Node 24 regardless.