Micronaut 5.2.4 is a patch release that is mostly Python
Serguey Asael Shinder2 min readMicronaut Core 5.2.4 was published on 23 September 2026 at https://github.com/micronaut-projects/micronaut-core/releases/tag/v5.2.4, and the interesting thing about it is the shape of the changelog rather than any single entry.
Three fixes concern the HTTP layer: cookies are no longer kept in the JDK raw HTTP client, each URI route is returned once from the router's uriRoutes(), and the connection is closed when a streamed client response is abandoned.
Everything after that is Python. More than a dozen entries carry the prefix, and they are not cosmetic: inherited constraints on the parameters of an overridden interface method; importing the package of a class before the module named after it; an override without a return hint taking the inherited return type; a PEP 695 method type parameter keeping its bound; checked exceptions declared on overrides of Java methods; bytes reaching an erased Object parameter arriving as a byte array; a custom scope proxy creating its target lazily; an instance attribute shadowing an intercepted method on self.
What it means
A changelog is a roadmap nobody writes down, and this one says Micronaut is building a Python front end in earnest. Nothing in the release announces it. But the specific bugs being fixed are the bugs you only meet once real code is running: generics bounds surviving a language boundary, checked exceptions crossing into a language that has none, interception interacting with attribute lookup on self. Those are integration problems, not prototype problems.
The pairing of PEP 695 with checked exceptions is the tell. One is recent Python type-parameter syntax; the other is a Java concept Python does not have. Fixing both in the same release means the work is not "run Python somehow" but "make the two type systems agree at the seam" - which is the expensive part and the part that decides whether such a bridge is usable.
⚠️ This reads a public changelog and no more. Micronaut has not made an announcement about scope or timelines here, and none is implied: what is reported is which fixes shipped on 23 September.