The platform's runtime moves to JDK 24 and GraalVM 24.2.1 in this release, with Gradle 8.14 picking up the new toolchain. The upgrade is the second major Java step after the JDK 21 baseline that landed in March 2024 ; it is the foundation the platform's late-2025 and early-2026 work builds on — virtual threads at scale, ClassFile API for ProGuard compatibility, structured-concurrency previews, GraalVM polyglot Python support.
- Virtual threads stable. JEP 444's finalisation in JDK 21 made virtual threads production-grade ; JDK 24's JIT and scheduler refinements make them comfortable at thousands-of-threads-per-process scale. The platform-wide VirtualThreadExecutor (shipped later in 2025-11) builds on this floor.
- GraalVM 24.2.1 JIT. The platform's server-side scripting surface — JavaScript via GraalVM, Python via GraalPy — runs inside the same JVM as the rest of the runtime, so the GraalVM JIT improvements flow through to user-authored scripts as well as to platform internals.
- ClassFile API. The new standard ClassFile API replaces the deprecated
sun.misc.Unsafebytecode paths the platform's earlier ProGuard configuration relied on, future-proofing the bytecode-optimisation step. - Gradle 8.14. The build toolchain moves to the version that recognises JDK 24 natively, eliminating the workaround configuration that the JDK-23-on-Gradle-8.13 path required.
JDK 24 is a six-month release ; the platform's LTS landing is JDK 25, which followed on 2026-03-12. The interim step matters because it carried the virtual-thread maturity that the platform's high-concurrency surfaces — JDBC pool tier-3, AI agent parallel execution, SSE streaming — depend on at scale.