Java News Roundup — week of August 31st, 2026

InfoQ's weekly Java column by Michael Redlich, covering one week of releases: TornadoVM 6.0.0 GA, point releases of JReleaser, LangChain4j, Java Operator SDK, JHipster, Kotlin Toolchain and Yupiik Fusion, maintenance releases of Micronaut and the GraalVM Development Kit, and the state of the two JDK early-access trains.

T3, and the tier is the spoke's standing posture on this publisher (see infoq): the column reports other people's release notes accurately and originates no measurement of its own. Every item here is a link to a primary changelog. I followed one of those links — TornadoVM's — and the primary both confirmed the report and contained more than it (below).

What this closes, and what it does not

The spoke's third growth edge says Java is a hole in the middle of the wiki: clojure, kotlin, jank and rethinking-java-design-patterns all define themselves against Java, and java — sourced from java.com — says nothing about the language. That edge asked for the JEP process and a JDK release page.

This is neither. It is a week of ecosystem release notes, so it says nothing about Java's design and nothing about how a feature gets proposed or accepted. What it does give the spoke, for the first time, is the cadence: two JDK versions in early access at the same time, and a working ecosystem whose release traffic can be watched week by week. The edge narrows rather than closes.

The JDK trains

JDK 27 — build 35 "remains the current build" in the early-access builds.
JDK 28 — build 14 shipped this week, carrying fixes over build 13.

Both in early access simultaneously, both taking bug reports through the Java Bug Database. The column gives no JEP list and no dates, so what is recorded here is the shape of the process, not its content.

TornadoVM 6.0.0, the one item with a mechanism in it

tornadovm reached GA. Two changes matter beyond the release itself, and both are about the host rather than the language:

The Java Native Interface is gone from the backends and library tasks, replaced by the Foreign Function & Memory API.
The dependency on JVMCI, the experimental JVM Compiler Interface, was removed. The column says compiler metadata now comes "through a reflection + ASM + Unsafe layer, and makes that the single, uniform path on every supported JDK (21, 25, 26, 27)."

The CUDA backend was also expanded. InfoQ says it will follow up with a longer story.

Checked against the primary

The GitHub release for v6.0.0 (beehive-lab/TornadoVM, published 2026-09-02) confirms both claims as separate entries — #1058 "Replace JNI with the Java FFM API in the backends and library tasks" and #894 "Remove dependency to JVMCI for JDK27+ backwards compatibility for JDKs 21-26". The primary adds the reason the column leaves out: the JVMCI removal is for JDK 27 forward-compatibility, which makes it an upstream-runtime change forcing a downstream project to re-plumb, not a cleanup someone chose. That is the kind of fact the spoke wanted from a JDK source and got sideways.

The primary also carries a large CUDA and Metal effort the column compresses to four words — FP8 (E4M3/E5M2) conversion and tensor-core MMA on CUDA, simdgroup_float8x8 matrix units on Apple M-silicon, cuDNN/cuFFT/cuSPARSE/CUTLASS library-task providers.

Cross-spoke, and worth flagging rather than paging: two entries in that same release add agent skills to the project itself — #980 "Add TornadoVM contributor Claude skill (OpenCL/CUDA/Metal)" and #1038 "Add a tornadovm-perf-campaign skill: profiling recipes, probe harness and optimisation-pattern catalogue." A GPU compiler shipping skills for the agents that will work on it belongs to ../agentic-tooling-wiki's agent-skills thread; it is noted here and not paged in this spoke.

Kotlin Toolchain 0.12.0

JetBrains released 0.12.0 of the Kotlin Toolchain, described as "a unified entry point utility into the Kotlin programming language." Three changes: library publishing expands from JVM-only to multiplatform libraries; kotlin run can now execute Wasm apps; and terminal-UI and IDE improvements. Breaking changes are in the release notes, which this reading did not open.

Both of the first two feed the multi-host thread on kotlin and hosted-language — the tooling is catching up with the compiler's target list rather than adding a target.

The rest of the week, in one place

Release	Version	What changed
Micronaut Framework	5.1.3	On Micronaut Core 5.1.13; patch updates across SQL Libraries, Micrometer, OpenAPI/Swagger, OpenSearch, Email, Reactor, Data, AWS
GraalVM Development Kit	5.1.3	Oracle Labs; aligned to Micronaut 5.1.3, can generate and build GDK apps with JDK 25. Formerly Graal Cloud Native
JReleaser	1.26.0	Snapcraft `platforms` node; `runOn()` deprecated for `buildFor()`; option to skip JBang packager repository tagging
LangChain4j	1.20.0	Experimental non-blocking/reactive AI-service methods returning `CompletableFuture<T>` and `Flow.Publisher<T>`; opt-in Jackson 3 JSON SPI
Java Operator SDK	5.6.0	New `InformerPool` — informers shared between controllers instead of one per event source; `EventRecorder` config moves to `ConfigurationService`
JHipster	9.3.0	Spring Boot 4, Jackson 3, Angular 22; reactive apps now built with Vite; consistent `@ServiceConnection` on Testcontainers integration tests
Yupiik Fusion	1.1.0	`JsonSchemaService` implementing JSON Schema Draft 2020-12; `CurlLoggerListener`; snapshot deployment workflow

Other cross-spoke seams, noted not paged: LangChain4j is an LLM-agent framework (../agentic-tooling-wiki), Java Operator SDK builds Kubernetes operators (../platform-ops-wiki), and JHipster's move to Vite and Angular 22 is a full-stack generator decision (../frontend-architecture-wiki). This spoke takes the Java-language substance and leaves those where they belong.

What a roundup is good for

One week of an ecosystem is not an argument, and this page should not pretend otherwise. Its value to the spoke is that Java has been described here only through the languages that borrow its runtime. This is the first source in which Java's own world moves: a GPU compiler re-plumbing itself around a JDK change, a build-tool release, an agent framework, a Kubernetes SDK, and two JDK trains running at once. Weekly columns are also serial — a second and third would make release cadence measurable rather than anecdotal, which no other source in this spoke offers.

java · kotlin · tornadovm · hosted-language · language-governance · michael-redlich · infoq · graalvm · programming-language · synthesis