Repository navigation
Support pinning java-version as "latest" #832
Description
Activity
Hi @aep-sunlife,
Thank you for creating this feature request. We will investigate it and provide feedback as soon as we have some updates.Hi @aep-sunlife, thank you for suggesting support for a java-version: latest option. While we recognize the benefits such as futureproofing CI pipelines and aligning with practices in other ecosystems. This feature currently hasn't received enough community interest or engagement.
We'll continue monitoring demand and revisit this in the future if more users indicate a need. In the meantime, we recommend explicitly specifying the desired Java version or using matrix builds to test against multiple versions.
Thanks again for your feedback and contribution!
This issue is scoped to a
latestalias only (resolve to the newest available version).The separate
ltsrequest (#847) is not being folded in here and has been declined —ltsis a vendor support/lifecycle classification, not an alias for "latest," and supporting it as a version selector would be complex and error-prone (which versions are "LTS" varies by vendor and changes over time). See #847 for the rationale.This issue (#832) remains open for the
latestalias.- linked a pull request that will close this issueSupport pinning java-version as "latest" #1091
on Jul 9, 2026 - added a commit that references this issue
on Jul 10, 2026
Description:
As a developer, I want to create a GitHub Actions job that tests my JVM projects against floating, bleeding edge Java versions. For comparison, workflows for other languages like Go support this with the
"latest"version value.Justification:
Today, I do not see an option to let the Java version automatically target the latest stable Java release version. Which breaks efforts at futureproof testing, with each new major release of Java.