Usually no. Non-LTS Java releases receive updates for about six months, until the next feature release arrives. Adoptium lists Java 26 as available until September 2026 and Java 27 until March 2027. Production fits an LTS release unless your team can upgrade twice a year without strain.
The facts
OpenJDK ships a feature release every six months. Since 2021, one every two years is designated LTS. The Adoptium support page lists these non-LTS releases:
| Release | First available | Available until |
|---|---|---|
| Java 26 | Mar 2026 | Sep 2026 |
| Java 27 | Sep 2026 | Mar 2027 |
Java 26's window has already closed as of this post. A service still on it is missing the quarterly security updates that follow.
When a non-LTS release makes sense
There are honest reasons to run one:
- You need a new language or runtime feature that is not in the current LTS.
- You have a mature upgrade pipeline and ship to the next release within weeks.
- The service is short lived or easy to redeploy.
There are poor reasons too: a developer installed the latest JDK and the Dockerfile copied it.
When it does not
- Third party frameworks often certify only against LTS releases.
- Vendors of commercial software often support only LTS.
- Long lived services need a stable base with a known end date.
The hidden cost is the compatibility work that repeats every six months, including checks for internals that moved. See Java 17 strong encapsulation for one example of what changes between releases.
A decision list
- Name the feature you need. If you cannot, use LTS.
- Check your framework's supported Java versions.
- Confirm you can roll a new JDK across all environments in under a month.
- Set a calendar reminder for six months out, when the release ends.
- If any answer is no, move to LTS. Java 25 is the newest in the Adoptium list.
Catch it with a policy
A check that flags any build image whose runtime is outside an allowed set is cheap. Policies can fail a pull request that introduces a non-LTS base image.
Try it yourself
Open the gate pull request demo and watch how a rule blocks a change. Imagine the rule says "runtime must be on the approved list."
Click through it at your own pace, or open it full screen.
Safeguard policies, gates and guardrails can enforce choices like this on pull requests. The free scan is at gold.safeguard.sh/scan.
Quick check
How often are Java feature releases published?
Every six months, per Adoptium's support page, with a new LTS every two years.
Can I run a non-LTS release in a throwaway test environment?
Yes, that is a sound use. Just keep it out of images that get promoted to production.
Sources
Last reviewed: 19 October 2026.
