Quarkus 3.40 is the new LTS with a year of support, as Quarkus 4 beta nears
Victoria Shinder1 min readThe Quarkus team has released version 3.40 and designated it the framework's new long-term support line. LTS releases are supported for 12 months, and the project says it is already working on the first beta of Quarkus 4.
For anyone already on 3.39 there is nothing to do: 3.40 is described as its direct continuation, with the core taken from 3.39 plus the fixes shipped in 3.40.1, and the 3.40 migration guide is empty for that reason.
The real audience is teams on the previous LTS, 3.33. Moving to 3.40 picks up five feature releases at once. The announcement lists them: JAR tree-shaking, profile-guided optimisation for native builds and Semeru AOT in 3.35; Quarkus Signals, embedded SBOMs and OIDC authentication with SPIFFE in 3.36; extension-based modularity, Hibernate ORM 7.4 and reflection-free Jackson serializers in 3.37; weight-based eviction for the Hibernate second-level Caffeine cache in 3.38; and post-quantum cryptography in the TLS registry in 3.39.
The recommended path is the Quarkus CLI's quarkus update, which the team says can update an application from any earlier version, including 2.x. It cautions that some cases still need manual work and asks users to read the migration guides for each version between 3.33 and 3.40. The project also notes that JobRunr 9 shipped with day-one support for the new LTS.
Why it matters
An LTS release is the version most production teams actually run, so the jump from 3.33 is where these features reach them. A 12-month window is short by enterprise standards, which makes the documented any-version update path the part worth testing first.