Skip to content

ci: bump actions/setup-java from v5 to v6 - #456

Open
kraenhansen wants to merge 1 commit into
mainfrom
claude/hopeful-hopper-fh5klm
Open

ci: bump actions/setup-java from v5 to v6#456
kraenhansen wants to merge 1 commit into
mainfrom
claude/hopeful-hopper-fh5klm

Conversation

@kraenhansen

Copy link
Copy Markdown
Collaborator

Summary

Audited every GitHub Action used across .github/workflows/check.yml and .github/workflows/release.yml against its latest available release. All actions are pinned to a floating major version tag/branch (@v7, @v6, @v4, @v2, @v1, etc.) that already tracks the latest release within that major line — except actions/setup-java, which was pinned to @v5 while @v6 (released 2026-08-24) is now the latest major.

hendrikmuhs/ccache-action is intentionally pinned to an exact patch (v1.2.23) rather than a floating tag; that pin already documents why (upstream's v1/v1.2 floating tags still point at an older, Node 20-based build) and I re-verified via git ls-remote that those floating tags still resolve to a stale commit, so the documented gate has not been unblocked and no change is needed there.

Change

Bumps all 6 occurrences of actions/setup-java (5 in check.yml, 1 in release.yml) from @v5 to @v6, keeping every usage at the same version.

v6.0.0's breaking changes (removal of legacy Adopt distributions, jdkFilejdk-file rename) don't affect our usage, which only passes java-version: "17" and distribution: "temurin".


Generated by Claude Code

v6.0.0 is now the latest major release. Our usage (java-version: 17,
distribution: temurin) isn't affected by v6's breaking changes (removal
of legacy Adopt distributions, jdkFile -> jdk-file rename).

Keeps all 6 occurrences of the action (5 in check.yml, 1 in
release.yml) at the same version.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants