How the world's leading engineering teams are tackling legacy code, eliminating technical debt, and modernizing their systems, with measurable results.
The first beta of Quarkus 4 lands with Java 21 as its new baseline, Netty 4.2 and Vert.x 5 underneath, opt-in HTTP/3 over QUIC, Hibernate ORM 8 on Jakarta Persistence 4.0, and Jackson 3. Final release is planned for the end of November. Note what the Java 21 baseline implies for anyone still on a javax-era stack: the modern Java runtime and the Jakarta namespace now arrive together, not separately.
GraalVM 25.4 ships new compiler optimization passes, Hibernate ORM 8.0 reaches its second and third betas against Jakarta Persistence 4.0, and Quarkus 3.39.5 closes 32 CVEs across the ecosystem it aggregates. A useful snapshot of how fast the native-first Java stack is moving, and of the patch cadence you inherit by staying current with it.
Quarkus 4 raises its minimum Java baseline to 21, aligning with Jakarta EE 11 and clearing the way for deeper native-image and virtual-thread integration. A clear signal of where native-first Java architecture is headed next.
Quarkus adds post-quantum cryptography support to its TLS Certificate Registry. Extension work that only reaches you if your native builds keep pace with the framework's release cadence, and a reminder that staying on an unsupported framework means opting out of this kind of security posture by default.
A walkthrough of the Spring Boot 2.x to 3.x upgrade, where the real cost is not the framework version but the Jakarta namespace change underneath it: every package renamed from javax to jakarta, and every library touching servlet, persistence or validation needing a compatible release. The same gate stands in front of a Quarkus migration, which is why we scope it first.