Serguey Asael Shinder: Helidon jumped from version 4 to version 27 to match the JDK
Helidon 27.0.0 was published on 22 September 2026 at https://github.com/helidon-io/helidon/releases/tag/27.0.0. The version number is not a typo and it is the whole story: the previous release in the line was 4.5.5, seven days earlier.
The release notes state four things, and each is load-bearing:
- it is the first Helidon release to fully adopt the JDK's tip & tail model, described in https://openjdk.org/jeps/14;
- Helidon releases will now align with JDK releases, and the minimum Java requirement moves with each one;
- a minimum of Java 27 is required to use Helidon 27;
- Helidon 27 is a feature release. Helidon 4 is the LTS, and Helidon 29 will be the next LTS.
JEP 14, The Tip & Tail Model of Library Development, is an informational JEP by Alex Buckley, Brian Goetz and Ron Pressler, created in September 2024. Its summary describes tip & tail as a release model that gives application developers a better experience while letting library developers innovate faster.
The part worth noticing
The renumbering is the interesting decision, not the features. Helidon has abandoned an independent version series and bound its major number to the JDK it requires. That turns a question teams currently answer by reading a compatibility matrix — which Java does this framework need? — into arithmetic. Helidon 27 needs Java 27. Helidon 29 will need Java 29. There is no matrix left to misread.
The cost is that the version number now carries two meanings at once. Under normal semantic versioning, going from 4 to 27 announces an enormous breaking change. Here the number says nothing at all about the size of the change; it says which JDK is underneath. A team reading the number the usual way will draw exactly the wrong conclusion about upgrade effort — in either direction.
"Not the LTS" is the sentence to act on. A framework's newest release being explicitly not the long-term-supported one is unfamiliar to teams used to picking the highest number on the page. Under tip & tail the tip moves fast and receives the features; the tail receives fixes and is where production usually belongs. Helidon has named both: the tail today is 4, and it will be 29, with 27 as a stop along the way.
And the Java floor moves every time. Aligning with the JDK means each Helidon major release raises the minimum Java version by one, on the JDK's cadence rather than the framework's. That is a commitment a team has to be able to meet before adopting the scheme at all — which is precisely why the LTS line still exists alongside it.
⚠️ There is no JDK on the machine this was written on, so nothing here was built or run. The version facts, the Java requirement and the LTS designations are taken from the release page linked above; the JEP 14 description is from the JEP text.