Micronaut Framework 5.0.0 Goes GA
The Micronaut team has released Micronaut Framework 5.0.0 as generally available, establishing JDK 25, Groovy 5, and Kotlin 2.3 as the new baseline requirements. This is a significant generational step for the framework: the IoC container has been refactored for improved startup performance, JSpecify nullability annotations are now supported throughout the core APIs, and the release ships programmatic retry and circuit breaker APIs for building resilient microservices without relying solely on annotation-based configurations.
The JSpecify integration is particularly relevant for teams building Kotlin and Java applications side by side — it enables tooling and static analysis to reason about nullability contracts without runtime overhead. The Kotlin 2.3 baseline also means full compatibility with the new Kotlin compiler K2 path. Teams upgrading from Micronaut 4.x should review the migration guide, as the JDK 25 requirement raises the minimum runtime from JDK 17 used in the 4.x line.
WildFly 40 GA: Full Jakarta EE 11 Support
WildFly 40 has reached general availability, delivering a comprehensive implementation of the Jakarta EE 11 specification. The release includes Jakarta Pages 4.0, WebSocket 2.2, and Authorization 3.0, bringing WildFly fully up to date with the EE 11 platform that formally standardized features from the Java EE 10 era. The Authorization 3.0 update is particularly notable — it replaces legacy role-based checks with a more expressive policy model that integrates with CDI and supports custom authorization interceptors.
The release also adds OpenID Connect logout functionality across multiple protocols, addressing a longstanding gap for enterprise deployments where single-logout across IdP and service provider sessions is a compliance requirement. WildFly 40 supports JDK 17 through JDK 26 and is the recommended upgrade path for teams on WildFly 36 or 37 who need Jakarta EE 11 certification.
Three New JEPs Proposed to Target JDK 27
Three new JEPs have been proposed to target JDK 27, rounding out what is shaping up as a significant release for JVM internals even as JDK 27 carries no new stable language features.
JEP 534 — Compact Object Headers by Default: This JEP promotes the experimental Compact Object Headers feature (originally shipped as opt-in in JDK 25 via JEP 519) to the default object header layout in HotSpot. Compact headers reduce the per-object overhead from 16 bytes to 8 bytes on 64-bit JVMs with compressed references, shrinking heap footprint meaningfully for object-heavy workloads. Making it the default removes the need for the experimental -XX:+UseCompactObjectHeaders flag and signals the optimization is production-ready.
JEP 536 — JFR In-Process Data Redaction: Java Flight Recorder gains the ability to apply redaction rules to sensitive field values before they are written to JFR recordings. This makes JFR safer for use in regulated environments where recording infrastructure-level events might inadvertently capture credentials, session tokens, or PII. The redaction operates at the JFR producer level, not at analysis time, so sensitive values never enter the recording stream.
JEP 528 — Post-Mortem Crash Analysis with jcmd: This JEP extends the jcmd diagnostic tool to support post-mortem analysis of JVM crash logs, enabling structured queries over hs_err files from the command line. Today, extracting root-cause information from crash dumps requires parsing raw text output; the new capability exposes a machine-readable interface that tooling and APM agents can query without custom parsers. JDK 27 rampdown phase one is scheduled for June 4, 2026, with GA targeted for September 14, 2026.
Apache Fory 1.0.0: Cross-Language Serialization Reaches Stable
Apache Fory has reached its 1.0.0 milestone, delivering a unified cross-language serialization format with first-class Java support. Fory introduces an annotation processor that generates schema-aware serializers at compile time for annotated Java classes, eliminating the runtime reflection overhead that plagues most JVM serialization libraries. The format supports Java, Python, Go, and JavaScript, making it a potential candidate for polyglot microservice architectures where JSON overhead becomes a bottleneck.
The 1.0.0 release focuses on API stability and cross-language wire compatibility guarantees. Unlike frameworks that are binary-compatible but not cross-language, Fory defines a shared schema model that carries type metadata needed for heterogeneous deserialization. Teams evaluating alternatives to Kryo or FST for high-throughput internal service calls should benchmark Fory's annotation-based path alongside their existing serializers.
