Skip to content

Pin CI to Liberica JDK 21.0.13 - #314

Closed
vpaturet wants to merge 1 commit into
masterfrom
ci/jdk-21.0.13
Closed

vpaturet wants to merge 1 commit into
masterfrom
ci/jdk-21.0.13

Conversation

@vpaturet

Copy link
Copy Markdown
Contributor

Summary

  • Pin every actions/setup-java step to Liberica JDK 21.0.13 (latest JDK 21 update, October 2026) instead of the floating 21.
  • Change the java_version input of the reusable maven-jreleaser-release.yml workflow from number to string (default "21.0.13"), since a number cannot hold a full version. deploy.yml passes "21.0.13" for snapshot publishing.

Note

The version is now pinned and needs a manual bump for future JDK 21 updates.

Replace the floating java-version 21 with the latest JDK 21 update in all
workflows. The java_version input of the reusable release workflow becomes
a string so it can hold a full version number.
@sonarqubecloud

Copy link
Copy Markdown

@vpaturet

Copy link
Copy Markdown
Contributor Author

Not needed: with java-version 21, setup-java already resolves the latest Liberica 21.x from BellSoft on every run (21.0.13+11 on master today). Pinning would only add manual bumps.

@vpaturet vpaturet closed this Oct 29, 2026
@vpaturet
vpaturet deleted the ci/jdk-21.0.13 branch October 29, 2026 15:44
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.

1 participant