| ✅ |
micronaut-acme |
6.2.x ✅ |
6.1.0 |
5.2.0 |
micronaut-projects/micronaut-acme#611 → 5.2.0 (merged) |
✅ |
48 tests, 0 failed |
| ✅ |
micronaut-aot |
3.2.x ✅ |
3.1.0 |
5.2.0 |
micronaut-projects/micronaut-aot#504 → 5.2.0 (merged) |
✅ |
64 tests, 0 failed |
| ✅ |
micronaut-aws |
5.2.x ✅ |
5.1.1 |
5.2.0 |
micronaut-projects/micronaut-aws#2588 → 5.2.0 (merged) |
✅ |
1407 tests, 0 failed (19 skipped) |
| ✅ |
micronaut-azure |
6.2.x ✅ |
6.1.0 |
5.2.0 |
— |
⚠️ |
6.2.x. 640 tests, 22 failed, all in the two Azure Function HTTP server TCK suites. 16 are CORS TCK tests (CorsSimpleRequestTest ×14, SimpleRequestWithCorsNotEnabledTest ×2), with 404 Not Found or a refresh count of 0: core #12880 moved these tests to a management endpoint, as for servlet and gcp. 5 are in the new ExplicitHeadRouteTest from core #13030: the X-Handler response header is missing even for a plain GET, which points to header handling in the Azure adapter. The last one, PublisherExceptionHandlerTest, was a connection reset under local load. A module-side fix task has been spawned; CI on micronaut-projects/micronaut-azure#1018 is still pending. Fix PR: micronaut-projects/micronaut-azure#1020 (function TCK suites). |
| ⬜ |
micronaut-cache |
6.2.x ✅ |
6.1.1 |
5.1.14 |
micronaut-projects/micronaut-cache#1055 → 5.2.0 |
✅ |
6.2.x, core c6158f9e0e. 200 tests, 0 failed. Fix PRs: micronaut-projects/micronaut-cache#1064 (audit on 6.2.x) and micronaut-projects/micronaut-cache#1065 (stop publishing a strict jackson-core constraint). |
| ✅ |
micronaut-cassandra |
7.2.x ✅ |
7.1.0 |
5.2.0 |
micronaut-projects/micronaut-cassandra#666 → 5.2.0 (merged) |
✅ |
7.1.x, core c6158f9e0e. 22 tests, 0 failed (on commit caa5f1d, the core 5.2 bump that micronaut-projects/micronaut-cassandra#666 re-applies on the new 7.2.x). |
| ✅ |
micronaut-chatbots |
2.2.x ✅ |
2.1.0 |
5.2.0 |
micronaut-projects/micronaut-chatbots#425 → 5.2.0 (merged) |
✅ |
653 tests, 0 failed |
| ✅ |
micronaut-coherence |
7.1.x ✅ |
7.0.1 |
5.2.0 |
micronaut-projects/micronaut-coherence#1059 → 5.2.0 (merged) |
— |
Not tested locally: the run was stopped after 106m with 0 test results; the Coherence system session never starts (SafeCluster restart loop, InjectorImplTest initializationError), a local cluster networking issue. Needs CI or a baseline run. |
| ⬜ |
micronaut-control-panel |
2.2.x ✅ |
2.1.0 |
5.1.12 |
micronaut-projects/micronaut-control-panel#659 → 5.2.0 |
⚠️ |
2.2.x. 263 tests, 0 failed, but three tasks fail dependency resolution before running: :micronaut-control-panel-ui:test and the doc example's inspectRuntimeClasspath and playwrightInstall. jackson-core cannot be resolved because micronaut-cache-infinispan 6.1.1 publishes {strictly 2.21.4} and micronaut-object-storage-gcp 3.1.0 publishes 2.18.9. It fails the same way in CI on micronaut-projects/micronaut-control-panel#659, and on 2.2.x since the move to cache 6.1.1 (not caused by the bump). Only cache-infinispan's strictly conflicts. Fixes: micronaut-projects/micronaut-control-panel#661 against 2.2.x (component metadata rule that relaxes the strict pin; jackson-core resolves to 2.22.1, 290 tests with 1 local Oracle container timeout), and root cause micronaut-projects/micronaut-cache#1065 against 6.1.x (plain constraint instead of strictly). |
| ✅ |
micronaut-crac |
3.2.x ✅ |
3.1.0 |
5.2.0 |
micronaut-projects/micronaut-crac#544 → 5.2.0 (merged) |
✅ |
36 tests, 0 failed (1 skipped) |
| ⬜ |
micronaut-data |
5.2.x ✅ |
4.14.5 |
5.1.12 |
micronaut-projects/micronaut-data#4035 → 5.2.0 |
⚠️ |
5.2.x, core snapshot. data-model and data-connection fail to compile: Reactor 3.8 marks block() @Nullable and NullAway treats that as an error, so data needs a fix. H2 tests (753): JdbcRepositorySpec failed intermittently because of introspection order, fixed in #13096. |
| ⬜ |
micronaut-discovery-client |
5.2.x ✅ |
5.1.0 |
5.1.7 |
micronaut-projects/micronaut-discovery-client#887 → 5.2.0 |
⚠️ |
5.2.x, core c6158f9e0e. 218 tests, 15 failed, all with one cause: the Consul client tests (ConsulMockAutoRegistrationSpec ×9, ConsulClientSpec, ConsulMockHealthStatusSpec, TtlHeartbeatSpec, CompositeDiscoverySpec, ClientScopeSpec) fail with InvalidFormatException: Cannot deserialize value of type java.net.InetAddress from String "<hostname>". Jackson 3.2.2, managed by core 5.2 (up from 3.1.4), no longer accepts a hostname for InetAddress. This affects Consul registration at runtime, not just tests. Baseline on core 5.1.7 (Jackson 3.1.x): 204 tests, 0 failed, so this comes from the Jackson upgrade. Fix: micronaut-projects/micronaut-discovery-client#897 (Consul addresses kept as strings; Consul tests and japiCmp pass on core 5.2.0 and 5.1.7). Update: fix micronaut-projects/micronaut-discovery-client#897 merged. |
| ⬜ |
micronaut-eclipsestore |
2.2.x |
2.1.0 |
5.1.6 |
micronaut-projects/micronaut-eclipsestore#325 → 5.2.0 |
✅ |
2.1.x, core c6158f9e0e. 108 tests, 2 failed: EclipseStoreMetricsBinderSpec and EclipseStoreMetricsBinderDisabledSpec get 404 Not Found from /metrics, the same regression as micronaut-sql and micronaut-kafka (released micronaut-micrometer endpoint not routed, #12960, fix in #13111). Baseline on core 5.1.6: eclipsestore 21/21 with all 20 test classes selected. Update: core #13111 merged into 5.2.x (6d53fc7); both EclipseStoreMetricsBinder*Spec pass against core 5.2.x head 6d53fc7. Needs a core 5.2.1 release. |
| ⬜ |
micronaut-elasticsearch |
6.2.x |
6.1.0 |
5.1.6 |
micronaut-projects/micronaut-elasticsearch#746 → 5.2.0 |
✅ |
6.1.x, core c6158f9e0e. 15 tests, 0 failed. Fix PR: micronaut-projects/micronaut-elasticsearch#745 (audit on 6.1.x). |
| ✅ |
micronaut-email |
3.3.x ✅ |
3.2.0 |
5.2.0 |
micronaut-projects/micronaut-email#653 → 5.2.0 (merged) |
✅ |
3.2.x, core c6158f9e0e. 284 tests, 0 failed. |
| ✅ |
micronaut-flyway |
8.2.x ✅ |
8.1.1 |
5.2.0 |
micronaut-projects/micronaut-flyway#907 → 5.2.0 (merged) |
✅ |
8.1.x, core c6158f9e0e. 32 tests, 1 failed: test-suite-oracle timed out starting the Oracle container ("DATABASE IS READY TO USE!" never logged), an environment issue that is not core related. |
| ✅ |
micronaut-gcp |
6.2.x ✅ |
6.1.0 |
5.2.0 |
— |
⚠️ |
6.1.x. 778 tests, 18 failed, all in the two GCP Function HTTP server TCK suites; the 2 ErrorHandler* ones are local-load flakes. Fixed in micronaut-projects/micronaut-gcp#1538 → 6.2.x (6.2.x created from 6.1.x HEAD; the PR carries the fix, the cherry-picked bump and 6.2.0-SNAPSHOT). Not core: micronaut-management already comes through the TCK. (1) GcpFunctionHttpServerUnderTest forced endpoints.refresh.enabled=false, so /refresh was 404; now a default. (2) GoogleFunctionHttpRequest.getParameters() URL-decoded multipart/form-data, so force=true never bound (200, refresh count 0). That is a production bug too; form fields now come from getParts(), which the embedded test server and HttpFunction.invoke now provide. No TCK test excluded. Local, --rerun-tasks: TCK 235 + 246 tests on core 5.2.0 and 224 + 231 on 5.1.9, 0 failed; function module checks green. |
| ✅ |
micronaut-graal-languages |
2.2.x ✅ |
2.1.0 |
5.2.0 |
micronaut-projects/micronaut-graal-languages#182 → 5.2.0 (merged) |
✅ |
4 tests, 0 failed |
| ✅ |
micronaut-graphql |
5.2.x ✅ |
5.1.0 |
5.2.0 |
micronaut-projects/micronaut-graphql#768 → 5.2.0 (merged) |
✅ |
5.1.x, core c6158f9e0e. 111 tests, 0 failed. |
| ✅ |
micronaut-groovy |
5.2.x ✅ |
5.1.0 |
5.2.0 |
micronaut-projects/micronaut-groovy#752 → 5.2.0 (merged) |
✅ |
5.1.x, core c6158f9e0e. 22 tests, 0 failed. |
| ⬜ |
micronaut-grpc |
5.2.x |
5.0.1 |
5.1.6 |
micronaut-projects/micronaut-grpc#1259 → 5.2.0 |
✅ |
5.1.x, core c6158f9e0e. 100 tests, 0 failed. |
| ✅ |
micronaut-guice |
2.2.x ✅ |
2.1.0 |
5.2.0 |
micronaut-projects/micronaut-guice#161 → 5.2.0 (merged) |
✅ |
2.2.x, core c6158f9e0e. 35 tests, 0 failed. |
| ⬜ |
micronaut-guides |
master |
— |
n/a |
— |
— |
|
| ✅ |
micronaut-hibernate-validator |
5.2.x ✅ |
5.1.0 |
5.2.0 |
micronaut-projects/micronaut-hibernate-validator#599 → 5.2.0 (merged) |
✅ |
5.1.x, core c6158f9e0e. 7 tests, 3 failed: ValidatedBeanSpec (invalid bean, custom validator, custom validator that is not a bean) fails with UnexpectedTypeException: Cannot find a constraint validator for constraint: org.hibernate.validator.constraints.URL and type: class java.lang.String, raised by DefaultValidator.validateConstrains during bean instantiation. The project uses released micronaut-validation 5.0.0. Baseline on core 5.1.1: 7/7 pass, so this is a core regression, bisected to #12859 (aeded4f). Update: not a core patch after all. The module-side fix micronaut-projects/micronaut-hibernate-validator#598 is merged on 5.1.x, and the core 5.2.0 bump micronaut-projects/micronaut-hibernate-validator#599 merged on the new 5.2.x with green CI. |
| ✅ |
micronaut-jackson-xml |
5.2.x ✅ |
5.1.0 |
5.2.0 |
micronaut-projects/micronaut-jackson-xml#569 → 5.2.0 (merged) |
✅ |
5.1.x, core c6158f9e0e. 26 tests, 0 failed. |
| ✅ |
micronaut-jakarta-el |
1.1.x ✅ |
1.0.0 |
5.2.0 |
micronaut-projects/micronaut-jakarta-el#20 → 5.2.0 (merged) |
✅ |
1.1.x, core c6158f9e0e. 1492 tests, 0 failed. |
| ✅ |
micronaut-jaxrs |
5.2.x ✅ |
5.1.0 |
5.2.0 |
micronaut-projects/micronaut-jaxrs#678 → 5.2.0 (merged) |
⚠️ |
5.1.x, core 5.2.0. The only 5.2 break is HttpMethodMapper: the switch (httpMethod) is not exhaustive after HttpMethod.QUERY was added (#12780). A default branch alone compiles, but a JAX-RS @HttpMethod("QUERY") resource then gets 405, because a custom method route is never matched for a QUERY request. micronaut-projects/micronaut-jaxrs#677 maps it to @Query. With it, check passes on 5.2.0 and matches a 5.1.12 baseline (TCK 2,764 tests, 1,074 skipped). Still needs a new 5.2.x branch for the bump. AnnotationReflectionUtils.resolveGenericToArgument can then move to ReflectionArguments. DefaultHttpClient.setHandlerRegistry has no public replacement: DefaultHttpClientBuilder.handlerRegistry is package-private. Update: fix micronaut-projects/micronaut-jaxrs#677 merged. |
| ✅ |
micronaut-jms |
5.2.x ✅ |
5.1.0 |
5.2.0 |
micronaut-projects/micronaut-jms#780 → 5.2.0 (merged) |
✅ |
5.1.x, core c6158f9e0e. 24 tests, 0 failed. |
| ✅ |
micronaut-jmx |
5.2.x ✅ |
5.1.0 |
5.2.0 |
micronaut-projects/micronaut-jmx#489 → 5.2.0 (merged) |
✅ |
5.2.x, core c6158f9e0e. 2 tests, 0 failed. |
| ⬜ |
micronaut-json-schema |
2.3.x |
2.2.0 |
5.1.11 |
micronaut-projects/micronaut-json-schema#406 → 5.2.0 |
✅ |
2.2.x, core c6158f9e0e. 510 tests, 0 failed. |
| ⬜ |
micronaut-kafka |
6.2.x ✅ |
6.1.0 |
5.1.7 |
micronaut-projects/micronaut-kafka#1399 → 5.2.0 |
✅ |
6.2.x, core c6158f9e0e. 377 tests, 8 failed. 6 are the /metrics 404 of released micronaut-micrometer 6.0.2 (KafkaListenerSpec, KafkaConsumerMetricsSpec, KafkaProducerMetricsSpec, KafkaStreamsMetricsSpec ×2, KafkaStreamsMetricsDisabledSpec), caused by #12960. UncaughtExceptionsSpec fails in cleanupSpec: its shared stopContext calls getBean on a context that is no longer running, which throws IllegalStateException since #12948. KafkaClientSpec "send when Kafka is not available" got TimeoutException instead of ExecutionException, and it fails on core 5.1.7 too. Baseline on core 5.1.7: kafka 297 tests with only that 1 failure; kafka-streams 40/40. Follow-up 2026-09-10: all 6 metrics specs pass against core with #13111 (full check 376 tests, 1 failed: the Groovy docs MyTest, which also fails on 5.1.7 and is fixed in micronaut-projects/micronaut-kafka#1398). UncaughtExceptionsSpec (early return in stopContext) and KafkaClientSpec (a 1 s get racing a ~1 s producer failure) are fixed in micronaut-projects/micronaut-kafka#1397. The core bump waits for a core release that includes #13111. Update: fix micronaut-projects/micronaut-kafka#1397 merged. Update: core #13111 merged into 5.2.x (6d53fc7); the metrics specs pass (0 failed) against core 5.2.x head 6d53fc7. Needs a core 5.2.1 release. |
| ⬜ |
micronaut-kotlin |
5.2.x |
5.1.0 |
5.1.10 |
micronaut-projects/micronaut-kotlin#913 → 5.2.0 |
✅ |
5.1.x, core c6158f9e0e. 89 tests, 0 failed. |
| ⬜ |
micronaut-kubernetes |
9.1.x |
9.0.0 |
5.1.13 |
micronaut-projects/micronaut-kubernetes#1146 → 5.2.0 |
✅ |
9.0.x, core c6158f9e0e. 420 tests, 2 failed, 106 skipped (no Kubernetes cluster locally). The 2 failures (kubernetes-operator ConfigMapResourceReconcilerSpec and ConfigMapResourceReconcilerWithFiltersSpec, "Failed to resolve the apiGroup for V1ConfigMap from discovery cache") need a live cluster for API discovery, and they fail the same way on core 5.1.13 (16 tests, same 2 failures). Not core related. |
| ⬜ |
micronaut-langchain4j |
2.3.x |
2.2.0 |
5.1.10 |
micronaut-projects/micronaut-langchain4j#379 → 5.2.0 |
⚠️ |
147 tests, 0 failed (45 skipped); run stopped after 95m in :test-suite:test on Ollama/Neo4j container ReadTimeouts — environment, not core Fix PR: micronaut-projects/micronaut-langchain4j#378 (KSP processor dependencies). |
| ✅ |
micronaut-liquibase |
7.2.x ✅ |
7.1.0 |
5.2.0 |
micronaut-projects/micronaut-liquibase#854 → 5.2.0 (merged) |
✅ |
7.1.x, core c6158f9e0e. 24 tests, 0 failed. |
| ✅ |
micronaut-logging |
2.2.x ✅ |
2.0.1 |
5.2.0 |
micronaut-projects/micronaut-logging#365 → 5.2.0 (merged) |
✅ |
2.1.x, core c6158f9e0e. Build and BOM check pass. The project has no test sources (test-suite compile and test tasks are NO-SOURCE), so no tests ran. |
| ⬜ |
micronaut-mcp |
2.1.x |
2.0.0 |
5.1.10 |
micronaut-projects/micronaut-mcp#218 → 5.2.0 |
✅ |
195 tests, 0 failed |
| ✅ |
micronaut-micrometer |
6.1.x ✅ |
6.0.2 |
5.2.0 |
micronaut-projects/micronaut-micrometer#1231 → 5.2.0 (merged) |
✅ |
6.1.x, core c6158f9e0e. 506 tests. 1 flaky failure in MetricsEndpointSpec (connection reset under load) passes on rerun. |
| ✅ |
micronaut-mongodb |
6.2.x ✅ |
6.1.0 |
5.2.0 |
micronaut-projects/micronaut-mongodb#989 → 5.2.0 (merged) |
✅ |
6.2.x, core c6158f9e0e. 54 tests, 0 failed. |
| ⬜ |
micronaut-mqtt |
4.2.x |
4.1.0 |
5.1.12 |
micronaut-projects/micronaut-mqtt#652 → 5.2.0 |
✅ |
4.1.x, core c6158f9e0e. 53 tests, 0 failed. |
| ✅ |
micronaut-multitenancy |
6.2.x ✅ |
6.1.0 |
5.2.0 |
micronaut-projects/micronaut-multitenancy#522 → 5.2.0 (merged) |
✅ |
6.2.x, core c6158f9e0e. 88 tests, 0 failed. |
| ✅ |
micronaut-nats |
5.2.x ✅ |
5.1.0 |
5.2.0 |
micronaut-projects/micronaut-nats#703 → 5.2.0 (merged) |
✅ |
5.1.x, core c6158f9e0e. 81 tests, 0 failed (on commit ecd5bda7, the core 5.2 bump that micronaut-projects/micronaut-nats#703 re-applies on the new 5.2.x). |
| ✅ |
micronaut-neo4j |
8.2.x ✅ |
8.1.0 |
5.2.0 |
micronaut-projects/micronaut-neo4j#675 → 5.2.0 (merged) |
✅ |
8.1.x, core c6158f9e0e. 3 tests, 0 failed. |
| ⬜ |
micronaut-object-storage |
3.2.x |
3.1.0 |
5.1.7 |
micronaut-projects/micronaut-object-storage#855 → 5.2.0 |
✅ |
3.1.x, core c6158f9e0e. 471 tests, 0 failed, 53 skipped (by module: object-storage-oracle-cloud 24, object-storage-azure 10, object-storage-aws 9, object-storage-gcp 8, object-storage-local 2). |
| ✅ |
micronaut-openapi |
7.3.x ✅ |
7.2.0 |
5.2.0 |
micronaut-projects/micronaut-openapi#2821 → 5.2.0 (merged) |
✅ |
7.2.x, core c6158f9e0e. 1387 tests, 0 failed. |
| ⬜ |
micronaut-openrewrite |
1.2.x |
1.1.0 |
5.1.7 |
micronaut-projects/micronaut-openrewrite#111 → 5.2.0 |
✅ |
Build passes; the module has no tests (test task NO-SOURCE) Fix PR: micronaut-projects/micronaut-openrewrite#110 (audit, micrometer-core 1.16.7). |
| ⬜ |
micronaut-opensearch |
2.2.x |
2.1.1 |
5.1.12 |
micronaut-projects/micronaut-opensearch#323 → 5.2.0 |
✅ |
2.1.x, core c6158f9e0e. 37 tests, 0 failed. |
| ⬜ |
micronaut-oracle-cloud |
6.2.x ✅ |
6.1.3 |
5.1.11 |
micronaut-projects/micronaut-oracle-cloud#1371 → 5.2.0 |
✅ |
6.2.x, core c6158f9e0e. oraclecloud-function-http fails 15/27 tests with a ClassCastException from the introspection bean class loader fallback in DefaultBeanIntrospector. Fixed by #13109 (27/27 pass with it). The other failures are OCI config or pre-existing. Update: core #13109 is merged into 5.2.x (1154498); :micronaut-oraclecloud-function-http:test passes 27/27 (1 @PendingFeature skipped) against core 5.2.x head 1d17e8f. Needs a core 5.2.1 release. |
| ✅ |
micronaut-picocli |
6.2.x ✅ |
6.1.0 |
5.2.0 |
micronaut-projects/micronaut-picocli#563 → 5.2.0 (merged) |
✅ |
6.1.x, core c6158f9e0e. 25 tests, 0 failed. |
| ⬜ |
micronaut-problem |
5.1.x ✅ |
5.0.0 |
5.1.3 |
— |
⚠️ |
5.1.x, core c6158f9e0e. 25 tests, 1 failed: DataLeakageOverrideSpec overrides shouldIncludeErrorMessageAsDetailForDefaultProblem and expects the detail "Internal Server Error: foo data", but gets "Internal Server Error". Core 05421f2 no longer includes the exception message in the error message by default (micronaut.server.error-response-include-message=never) and exposes it as ErrorContext.getExceptionMessage(), so micronaut-problem should build the detail from that. Fix: micronaut-problem-json#568 (27 tests pass on core 5.1.3 and 5.2.0; no other 5.2-only failures). Update: fix micronaut-projects/micronaut-problem-json#568 merged. |
| ⬜ |
micronaut-projectgen |
1.2.x |
1.1.0 |
5.1.6 |
micronaut-projects/micronaut-projectgen#398 → 5.2.0 |
✅ |
773 tests, 0 failed (13 skipped) |
| ⬜ |
micronaut-pulsar |
3.2.x |
3.1.0 |
5.1.6 |
micronaut-projects/micronaut-pulsar#855 → 5.2.0 |
✅ |
3.1.x, core c6158f9e0e. 21 tests, 0 failed. |
| ✅ |
micronaut-r2dbc |
7.2.x ✅ |
7.0.2 |
5.2.0 |
micronaut-projects/micronaut-r2dbc#1045 → 5.2.0 (merged) |
✅ |
7.2.x, core c6158f9e0e. 44 tests, 0 failed. |
| ⬜ |
micronaut-rabbitmq |
5.2.x |
5.1.0 |
5.1.11 |
micronaut-projects/micronaut-rabbitmq#874 → 5.2.0 |
✅ |
5.1.x, core c6158f9e0e. 97 tests, 1 failed: Kotlin docs example HeadersSpec throws RabbitClientException: The @RabbitHeaders annotation is applied to an argument that is not java.util.Map<String, ?>. ProductClient.send(@RabbitHeaders headers: Map<String, Any>) compiles to Map<String, ? extends Object>, which is now a WildcardArgument (#13023). DefaultArgument.equalsType compares nested type parameters with equals, and DefaultWildcardArgument.equals requires the other side to be a wildcard too, so argument.equalsType(Argument.mapOf(String.class, Object.class)) is false. It passes on core 5.1.11 (HeadersSpec 1/1 with Predictive Test Selection disabled). Core regression. Fix: #13115 (not fixed by #13109/#13111/#13114; control retest still fails). Update: core#13115 merged into 5.2.x (fc92af4). |
| ✅ |
micronaut-reactor |
4.3.x ✅ |
4.2.0 |
5.2.0 |
micronaut-projects/micronaut-reactor#677 → 5.2.0 (merged) |
✅ |
4.2.x, core c6158f9e0e. 26 tests, 0 failed. |
| ✅ |
micronaut-redis |
7.2.x ✅ |
7.1.0 |
5.2.0 |
micronaut-projects/micronaut-redis#819 → 5.2.0 (merged) |
✅ |
7.1.x, core 5.2.0 (merged bump 9d5fce72). 156 tests, 0 failed. Note: the bump landed on a patch branch of the released 7.1 minor (see "Core 5.2 must land in a new minor"). |
| ⬜ |
micronaut-rss |
5.2.x ✅ |
5.1.0 |
5.1.13 |
micronaut-projects/micronaut-rss#548 → 5.2.0 |
✅ |
5.2.x, core c6158f9e0e. 80 tests, 0 failed. |
| ✅ |
micronaut-rxjava3 |
4.2.x ✅ |
4.1.0 |
5.2.0 |
micronaut-projects/micronaut-rxjava3#545 → 5.2.0 (merged) |
✅ |
4.2.x, core c6158f9e0e. 10 tests, 0 failed. |
| ✅ |
micronaut-security |
5.4.x ✅ |
5.3.2 |
5.2.0 |
micronaut-projects/micronaut-security#2278 → 5.2.0 (merged) |
⚠️ |
5.4.x, core c6158f9e0e. 1675 tests. BuiltInEndpointsSpec (sensitive endpoint without a SensitiveEndpointRule replacement) fails every time: the 500 response no longer includes the exception message, because core 05421f2 added micronaut.server.error-response-include-message with default never. The test needs updating. SecuredExpressionSpec was flaky and passes on rerun. Update: fix micronaut-projects/micronaut-security#2277 merged. |
| ⬜ |
micronaut-serialization |
3.2.x |
3.1.1 |
5.1.3 |
micronaut-projects/micronaut-serialization#1415 → 5.2.0 |
⚠️ |
3.2.x, core snapshot. @JsonIgnoreProperties inheritance regression, fixed in #13099. 6 failures in test-suite-tck-jackson-databind come from Jackson 3.1.4 → 3.2.2. With micronaut-projects/micronaut-serialization#1415: check passes on 5.2.x c6158f9e0e (0 failures). On 5.2.0 only the SerdeJsonIgnoreAllowSpec inheritance case fails, fixed in 5.2.1 by #13099. test-suite-http-server-tck-netty is flaky locally (connection closed, a different test each run). |
| ⬜ |
micronaut-servlet |
6.2.x |
6.1.0 |
5.1.3 |
micronaut-projects/micronaut-servlet#1123 → 5.2.0 |
⚠️ |
6.2.x, core c6158f9e0e. 1883 tests, 34 failed, all module-side. 28 are 7 CorsSimpleRequestTest tests × the Tomcat, Undertow, JDK and POJA-Apache TCK suites (refresh count 0): #12880 made the CORS TCK call the management /refresh endpoint, and servlet's TCK suites lack micronaut-management. 4 are the Jetty, Tomcat and Undertow *ErrorSpec streaming error tests and Jetty FilterErrorSpec, which expect the exception message that core 05421f2 now hides by default (micronaut.server.error-response-include-message=never). 2 are POJA-Apache SimpleRequestWithCorsNotEnabledTest 404s with the same cause: #12880 rewrote that test to call /refresh too. Baseline on core 5.1.3: all 34 of these pass. |
| ✅ |
micronaut-session |
5.2.x ✅ |
5.1.0 |
5.2.0 |
micronaut-projects/micronaut-session#380 → 5.2.0 (merged) |
⚠️ |
5.2.x, core c6158f9e0e. 36 tests, 0 failed, but :micronaut-docs-examples:micronaut-example-kotlin:compileTestKotlin fails: ShoppingControllerTest.kt calls .body() and .header() on Flux...blockFirst(), which Reactor 3.8 (managed by core 5.2) marks @Nullable, so Kotlin types it HttpResponse<Cart>?. The docs example needs !! or safe calls. Same Reactor 3.8 nullability cause as micronaut-data; no core API change. It compiles on core 5.1.10 (Reactor 3.7). Update: session#381 is merged; Renovate rebased micronaut-projects/micronaut-session#380 onto it and build (25) now passes. build_matrix failed on an HTTP 500 from services.gradle.org and is being rerun. |
| ⬜ |
micronaut-sourcegen |
2.2.x |
2.2.0 |
5.1.10 |
— |
⚠️ |
2.2.x, core c6158f9e0e. 1550 tests, 1 failed: test-suite-kotlin HeronTest asserts getAnnotationValuesByType(Heron.Boo) returns 1, but core 5.2 returns 2. The test comment already says "There should actually be 2 Boo annotations", so this is core fixing repeatable annotation resolution. The test should expect 2 and re-enable the bam assertion. Baseline on core 5.1.10: test-suite-kotlin 68/68, so the change comes from core 5.2. |
| ✅ |
micronaut-spring |
6.2.x ✅ |
6.1.0 |
5.2.0 |
micronaut-projects/micronaut-spring#864 → 5.2.0 (merged) |
✅ |
6.2.x, core c6158f9e0e. 66 tests, 0 failed. |
| ⬜ |
micronaut-sql |
7.2.x ✅ |
7.1.2 |
5.1.13 |
micronaut-projects/micronaut-sql#2100 → 5.2.0 |
✅ |
7.2.x, core c6158f9e0e. 446 tests, 68 failed: every DataSourcePoolMetadataSpec feature in jdbc-hikari (32), jdbc-tomcat, jdbc-dbcp and jdbc-ucp (12 each) gets 404 Not Found from the /metrics endpoint of released micronaut-micrometer 6.0.2. The same modules pass on core 5.1.13. This is a core regression: bisected to #12960 (d44e268). Update: core #13111 merged into 5.2.x (6d53fc7); the jdbc-hikari/-tomcat/-dbcp/-ucp pool metadata specs pass (47 tests, 0 failed) against core 5.2.x head 6d53fc7. Needs a core 5.2.1 release. |
| ✅ |
micronaut-test |
5.2.x ✅ |
5.1.1 |
5.2.0 |
micronaut-projects/micronaut-test#1517 → 5.2.0 (merged) |
✅ |
5.1.x, core c6158f9e0e. 261 tests, 0 failed. |
| ⬜ |
micronaut-test-resources |
4.3.x |
4.2.0 |
5.1.11 |
micronaut-projects/micronaut-test-resources#1214 → 5.2.0 |
⚠️ |
4.2.x. 398 tests, 12 failed. One is caused by core 5.2: TestResourcesClientTest "reasonable error message" gets "Internal Server Error" instead of the server's message, because core 05421f2 sets micronaut.server.error-response-include-message to never. This also hides test resources service errors from users; a module-side fix task has been spawned. The other 11 are local environment problems: 8 Oracle XE and MongoDB container start timeouts, 2 IntellijIdeaDatasourceExporterStandaloneProjectTest nested builds that cannot see the local core snapshot, and 1 macOS BindException in the H2 loopback test. Fix PR: micronaut-projects/micronaut-test-resources#1212. |
| ✅ |
micronaut-toml |
3.2.x ✅ |
3.1.0 |
5.2.0 |
micronaut-projects/micronaut-toml#371 → 5.2.0 (merged) |
✅ |
3.1.x, core c6158f9e0e. 1152 tests, 0 failed. |
| ⬜ |
micronaut-tracing |
8.3.x ✅ |
8.2.0 |
5.1.7 |
micronaut-projects/micronaut-tracing#936 → 5.2.0 |
✅ |
8.3.x, core c6158f9e0e. 185 tests, 0 failed. :micronaut-tracing-bom:checkBom fails on the third-party opentelemetry-instrumentation-bom 2.30.0 (it declares opentelemetry-semconv from another group and imports another BOM). Not core related; suppress it in micronautBom or align OpenTelemetry. |
| ⬜ |
micronaut-validation |
5.2.x ✅ |
5.1.0 |
5.1.11 |
micronaut-projects/micronaut-validation#684 → 5.2.0 |
✅ |
5.2.x, core c6158f9e0e. 932 tests, 33 failed. 32 are Jakarta Validation TCK failures (constraint inheritance, group sequence inheritance, cross-parameter and generic validator resolution, property paths, ConstraintValidatorContext); the same TCK passes 384/384 on core 5.1.11, so this is a core regression, bisected to #12977 (2c9161c, add the micronaut-reflection module). Fixed by #13114: the TCK passes 384/384 on 5.2.x + #13109/#13111/#13114. The other is ValidatorSpec "@introspected is required to validate the bean", a known 5.2 behaviour change (500/500 on 5.1.11). Update: core #13114 merged into 5.2.x (9089b06); the Jakarta Validation TCK passes 384/384 against core 5.2.x head fc92af4. Needs a core 5.2.1 release. |
| ✅ |
micronaut-views |
6.3.x ✅ |
6.2.0 |
5.2.0 |
micronaut-projects/micronaut-views#1190 → 5.2.0 (merged) |
⚠️ |
6.3.x, core c6158f9e0e. 587 tests, 2 failed. FreemarkerViewRendererSpec expects "Internal Server Error: View [bogus] does not exist", which core 05421f2 now hides by default (micronaut.server.error-response-include-message=never), so the test needs updating. TurboFrameSpec "/frame/disabled" hit a connection reset under load; it is flaky and passes 26/26 on 3 reruns. Baseline on core 5.1.7: views-freemarker 13/13 and views-turbo 99/99. |
Tracking issue for moving every project managed by the Micronaut Platform 5.2 onto Micronaut Core 5.2.x (latest: 5.2.0, released 2026-09-10; the platform catalog still pins
5.1.14).Progress: 40/71 projects on core 5.2 · 69/71 tested against 5.2 (54 ✅ pass · 15⚠️ issues found · 0 ❌ open core regression · 0 ⏳ running)
For each project:
Legend: ⬜ not on core 5.2 yet · ✅ on core 5.2 · Test column: ✅ passes ·⚠️ issues found (fixed or module-side) · ❌ open core regression · ⏳ running · — not tested yet
Core under test:
5.2.xat c6158f9 (5.2.1-SNAPSHOT, includes the fixes below) or the equivalent 5.2.0 release code. Core issues found so far:@JsonIgnorePropertiesinheritance)/metricsmanagement endpoint of released micronaut-micrometer 6.0.2 (compiled against core 5.1) returns 404 on core 5.2, which breaks micronaut-sqlDataSourcePoolMetadataSpec, 6 micronaut-kafka metrics specs and 2 micronaut-eclipsestore metrics specs. Bisected to Enumerate beans by their @Indexed types even when not implemented #12960 (d44e268, enumerate beans by their@Indexedtypes); fix in Find beans compiled before their annotation was self-indexed #13111oraclecloud-function-http; verified 27/27 with the fix)java.net.InetAddressno longer deserializes from a hostname. This breaks micronaut-discovery-client Consul registration (15 tests) and serde'sInetAddressTest(databind variant adapted in Update to Micronaut Core 5.2 micronaut-serialization#1415; serde'sInetAddressSerdestill resolves hostnames, pending this decision). Decide whether core keeps 3.2.2 (and modules adapt, e.g. keep the address as aStringor configure the deserializer) or pins or configures Jackson — proposed module-side fix: Keep Consul addresses as the strings Consul sends micronaut-discovery-client#897 keeps Consul addresses as strings (no DNS in deserialization), so core can keep Jackson 3.2.2 Merged (discovery-client#897 on5.2.x).@URLonString) are no longer found byDefaultValidatorwhen a@Validatedbean is created on core 5.2 (ValidatedBeanSpec, 3/7; 7/7 on core 5.1.1). It uses the released micronaut-validation 5.0.0. Bisected to fix: allow validated @Value constructor params without @Introspected #12859 (aeded4f, allow validated @value constructor params without @introspected); investigation session running; fix in Validate injected values with Hibernate Validator micronaut-hibernate-validator#598 (against5.1.x)Argument.equalsTypeno longer matches a KotlinMap<String, Any>(or otherout-variance) argument againstArgument.mapOf(String, Object): since Compile a wildcard type argument to a WildcardArgument that keeps its bounds #13023 the nested? extends Objectis aWildcardArgument,DefaultArgument.equalsTypecompares type parameters withequals, andDefaultWildcardArgument.equalsrejects a plain argument. This breaks micronaut-rabbitmq@RabbitHeaders(Kotlin docsHeadersSpec) at runtime, and Compile a wildcard type argument to a WildcardArgument that keeps its bounds #13023 intendedequalsTypeto ignore bounds — fix Compare nested type arguments by type in equalsType and typeHashCode #13115Module-side follow-ups:
@Nullableblock()inBlockingReactorRepositoryOperationsandSynchronousConnectionOperationsFromReactiveConnectionOperationstest-suite-tck-jackson-databindexpectations for Jackson 3.2, in Update to Micronaut Core 5.2 micronaut-serialization#1415 (core 5.2.0 bump on3.2.xat3.2.0-SNAPSHOT, cbor 3.2.2). The databind variant runs the 3 conflicting@JsonTypeInfocases withEXISTING_PROPERTYthrough a base-spec hook, expects{}for class-levelNON_DEFAULTnull, and replacesInetAddressTestwith a no-DNSDatabindInetAddressSpec. It also drops the now-passing@PendingFeatureandCompoundLocaleObjectMapperListener. Serde's own behaviour is unchanged.checkpasses on 5.2.xc6158f9e0e; on 5.2.0 onlySerdeJsonIgnoreAllowSpecinheritance fails (Keep a property's annotations to the type it is read through #13099); review requestedmicronaut-managementto the HTTP server TCK suites;CorsSimpleRequestTestandSimpleRequestWithCorsNotEnabledTestcall/refreshsince Use management refresh endpoint in CORS TCKs #12880 (30 failures). Servlet parity, waves 1 and 2: multipart, body-less requests, JDK server, request cleanup micronaut-servlet#1123 excludesSimpleRequestWithCorsNotEnabledTeston POJA but doesn't add the dependency, and it re-enablesCorsSimpleRequestTeston Jetty; its CI is pendingFilterErrorSpecformicronaut.server.error-response-include-message(defaultnever), done in Servlet parity, waves 1 and 2: multipart, body-less requests, JDK server, request cleanup micronaut-servlet#1123AbstractTestContainersSpec.stopContext(kafka-streams) callsgetBeanon a context that is no longer running, which throwsIllegalStateExceptionsince Throw IllegalStateException when resolving beans from a context that is not running #12948 and failsUncaughtExceptionsSpec.cleanupSpec; fix in Fix kafka tests failing on Micronaut Core 5.2 micronaut-kafka#1397ShoppingControllerTest.ktneeds!!or safe calls afterblockFirst()(Reactor 3.8@Nullable), fix in Assert non-null on blockFirst() in the Kotlin docs example micronaut-session#381FreemarkerViewRendererSpecformicronaut.server.error-response-include-message(defaultnever), fix and core 5.2.0 bump in Fix Freemarker error message test for core 5.2 and update core to 5.2.0 micronaut-views#1190 (on the unreleased6.3.x)HttpMethod.QUERY(Add RFC 10008 support (QUERY Method) #12780) injaxrs-processorHttpMethodMapperto@Query; a plaindefaultbranch compiles but QUERY requests get 405. Fix in Map the QUERY HTTP method to Micronaut's @Query micronaut-jaxrs#677 (against 5.1.x, builds on core 5.1 and 5.2)shouldIncludeErrorMessageAsDetailForDefaultProblemis enabled, take the detail fromErrorContext.getExceptionMessage(); core 05421f2 removed the message from the default error message (DataLeakageOverrideSpec) — fix micronaut-problem-json#568: rebuilds the detail from the root cause (5.1.x compiles against core 5.1.3, which has nogetExceptionMessage());checkpasses on 5.1.3 and 5.2.0test-suite-kotlinHeronTestshould expect 2Heron.Boovalues fromgetAnnotationValuesByTypeand re-enable thebamassertion; core 5.2 now resolves both repeatable annotations, fix in Expect both repeated @Heron.Boo values in the Kotlin HeronTest (needs core 5.2) micronaut-sourcegen#511. Note: it targets2.2.x, whose 2.2.0 is released, and passes only on core 5.2; it belongs on a new2.3.xminorBuiltInEndpointsSpecfor the newmicronaut.server.error-response-include-messagesetting, which defaults tonever(core 05421f2) and removes the exception message from 500 responses, fix in Accept the 500 body without the exception message in BuiltInEndpointsSpec micronaut-security#2277Proposed core 5.2.1 patch release
Several 5.2 projects fail only because of core regressions. All of them are now fixed on
5.2.x. A core 5.2.1 release with these fixes unblocks them without changes in the projects. Verification publishes core from5.2.x, then reruns the previously failing tests of each affected project against it (--rerun, with test counts read from the XML reports).Merged into
5.2.xsince 5.2.04e56c0a69fJdbcRepositorySpec(flakyclienttable)c6158f9e0eSerdeJsonIgnoreAllowSpec"@JsonIgnoreProperties inheritance"1154498e80oraclecloud-function-http1d17e8fe58(15 failed before). No new failures in aws (1407 tests), azure, gcp, graal-languages or serialization9089b06da8equalsTypeandtypeHashCodefc92af42a4HeadersSpec(@RabbitHeadersonMap<String, Any>, #13023)/metrics404, #12960)6d53fc7bb4jdbc-hikari/-tomcat/-dbcp/-ucppool metadata specs; micronaut-kafka metrics specs; micronaut-eclipsestore metrics specsKafkaListenerSpec11,KafkaConsumerMetricsSpec1,KafkaProducerMetricsSpec1,KafkaStreamsMetricsSpec2,KafkaStreamsMetricsDisabledSpec2, 0 failed; ✅ eclipsestore bothEclipseStoreMetricsBinder*Spec, 0 failed on the PR head; again on the merged 5.2.x head6d53fc7bb4: sql 47 metadata tests, kafka metrics specs, eclipsestore metrics specs, 0 failedAll known core regressions are merged into
5.2.x(last: #13111 on 2026-09-11). Core 5.2.1 can be released.Bump PRs waiting for the 5.2.1 release:
6d53fc7bb4)Not fixed by a core patch
ValidatedBeanSpec(fix: allow validated @Value constructor params without @Introspected #12859,@Valuebeans skipvalidateBean): still fails 3/3 onfc92af42a4. The fix is module-side: Validate injected values with Hibernate Validator micronaut-hibernate-validator#598, merged on5.1.x; the 5.2.x core bump Fix subproject name so IntelliJ Gradle integration doesn't complain #599 is merged and green.InetAddresshostnames → micronaut-discovery-client Consul registration: Keep Consul addresses as the strings Consul sends micronaut-discovery-client#897, merged on5.2.x; the Renovate core 5.2 bump Update Micronaut dependencies micronaut-discovery-client#887 needs a branch update to pick it up.HeronTestrepeatable-annotation count).Core 5.2 must land in a new minor
Core 5.2 may only be merged into a new, unreleased minor of each library: the target branch must be at
X.Y.0-SNAPSHOT, and novX.Y.*release may exist yet. Patch branches of released minors must stay on core 5.1.Merged into a released minor, so these need moving to a new minor branch (revert on the patch branch, re-apply on
X.(Y+1).x):7.1.x(7.1.1-SNAPSHOT,7.1.0released): revert Revert core 5.2 bump on released minor 7.1 micronaut-cassandra#665; re-applied on the new7.2.x(7.2.0-SNAPSHOT) in Start 7.2.x at 7.2.0-SNAPSHOT with core 5.2.0 micronaut-cassandra#666 — done: revert (now core 5.1.14, netty 4.2.17) and re-apply both merged.2.1.x(2.1.1-SNAPSHOT,2.1.0released): revert Revert core 5.2 bump on released minor 2.1 micronaut-chatbots#424; re-applied on the new2.2.x(2.2.0-SNAPSHOT) in Start 2.2.x at 2.2.0-SNAPSHOT with core 5.2.0 micronaut-chatbots#425 — done: revert and re-apply both merged.5.1.x(5.1.1-SNAPSHOT,5.1.0released): revert Revert core 5.2 bump on released minor 5.1 micronaut-nats#702; re-applied on the new5.2.x(5.2.0-SNAPSHOT) in Start 5.2.x at 5.2.0-SNAPSHOT with core 5.2.0 micronaut-nats#703 — revert merged; re-apply Start 5.2.x at 5.2.0-SNAPSHOT with core 5.2.0 micronaut-nats#703 is green and awaiting approval.7.1.x(7.1.1-SNAPSHOT,7.1.0released): revert Revert core 5.2 bump on released minor 7.1 micronaut-redis#818; re-applied on the new7.2.x(7.2.0-SNAPSHOT) in Start 7.2.x at 7.2.0-SNAPSHOT with core 5.2.0 micronaut-redis#819 — done: revert (now core 5.1.14, netty 4.2.17) and re-apply both merged.5.1.x(5.1.2-SNAPSHOT,5.1.1released): revert Revert core 5.2 bump on released minor 5.1 micronaut-test#1516; re-applied on5.2.x(5.2.0-SNAPSHOT) in Update Micronaut dependencies to core 5.2.0 on 5.2.x micronaut-test#1517 — done: revert and re-apply both merged.Open bump PRs targeting a released minor, to retarget onto a new minor branch before merging:
7.0.x(7.0.2-SNAPSHOT,7.0.1released) — replacement on a new minor branch: Start 7.1.x at 7.1.0-SNAPSHOT with core 5.2.0 micronaut-coherence#10593.1.x(3.1.1-SNAPSHOT,3.1.0released) — replacement on a new minor branch: Start 3.2.x at 3.2.0-SNAPSHOT with core 5.2.0 micronaut-crac#5442.1.x(2.1.1-SNAPSHOT,2.1.0released) — replacement on a new minor branch: Start 2.2.x at 2.2.0-SNAPSHOT with core 5.2.0 micronaut-eclipsestore#3256.1.x(6.1.1-SNAPSHOT,6.1.0released) — replacement on a new minor branch: Start 6.2.x at 6.2.0-SNAPSHOT with core 5.2.0 micronaut-elasticsearch#7466.1.x(6.1.1-SNAPSHOT,6.1.0released); superseded by Core 5.2 on 6.2.x: bind multipart form fields and fix the HTTP server TCK micronaut-gcp#1538 →6.2.x(new branch, bump cherry-picked,6.2.0-SNAPSHOT)2.1.x(2.1.1-SNAPSHOT,2.1.0released)5.1.x(5.1.1-SNAPSHOT,5.1.0released) — replacement on a new minor branch: Start 5.2.x at 5.2.0-SNAPSHOT with core 5.2.0 micronaut-graphql#7685.1.x(5.1.1-SNAPSHOT,5.1.0released)2.2.x(2.2.1-SNAPSHOT,2.2.0released) — replacement on a new minor branch: Start 2.3.x at 2.3.0-SNAPSHOT with core 5.2.0 micronaut-json-schema#4062.2.x(2.2.1-SNAPSHOT,2.2.0released) — replacement on a new minor branch: Start 2.3.x at 2.3.0-SNAPSHOT with core 5.2.0 micronaut-langchain4j#3792.0.x(2.0.1-SNAPSHOT,2.0.0released) — replacement on a new minor branch: Start 2.1.x at 2.1.0-SNAPSHOT with core 5.2.0 micronaut-mcp#2183.1.x(3.1.1-SNAPSHOT,3.1.0released) — replacement on a new minor branch: Start 3.2.x at 3.2.0-SNAPSHOT with core 5.2.0 micronaut-object-storage#8557.2.x(7.2.1-SNAPSHOT,7.2.0released) — replacement on a new minor branch: Start 7.3.x at 7.3.0-SNAPSHOT with core 5.2.0 micronaut-openapi#28211.1.x(1.1.1-SNAPSHOT,1.1.0released) — replacement on a new minor branch: Start 1.2.x at 1.2.0-SNAPSHOT with core 5.2.0 micronaut-openrewrite#1113.1.x(3.1.1-SNAPSHOT,3.1.0released) — replacement on a new minor branch: Start 3.2.x at 3.2.0-SNAPSHOT with core 5.2.0 micronaut-pulsar#855Branches named for a new minor whose
projectVersionstill belongs to the released one (bumpprojectVersiontoX.Y.0-SNAPSHOTfirst):1.1.xis at1.0.1-SNAPSHOT5.1.xis at5.0.0-SNAPSHOT3.2.xis at3.1.2-SNAPSHOT(bump PR Update to Micronaut Core 5.2 micronaut-serialization#1415)6.2.xis at6.1.1-SNAPSHOT(bump PR Servlet parity, waves 1 and 2: multipart, body-less requests, JDK server, request cleanup micronaut-servlet#1123)Projects not on the correct new minor branch
40/71 done: core 5.2 on a new, unreleased minor branch (
X.Y.0-SNAPSHOT, newer than the latest release) that is also the default branch, so Renovate and the common-files sync target it. Remaining projects, by what is left:Bump PR failing (16)
2.2.x2.2.x5.1.12→ 5.25.2.x5.2.x5.1.12→ 5.25.2.x5.2.x5.1.7→ 5.22.2.x2.2.x5.1.6→ 5.26.2.x6.2.x5.1.7→ 5.22.3.x2.3.x5.1.10→ 5.26.2.x6.2.x5.1.11→ 5.25.1.x5.1.x5.1.3→ 5.23.2.x3.2.x5.1.6→ 5.2micronaut-projects/micronaut-pulsar#854 (❌ failing, approved)
5.2.x5.2.x5.1.11→ 5.25.2.x5.2.x5.1.13→ 5.23.2.x3.2.x5.1.3→ 5.26.2.x6.2.x5.1.3→ 5.27.2.x7.2.x5.1.13→ 5.28.3.x8.3.x5.1.7→ 5.25.2.x5.2.x5.1.11→ 5.2CI cancelled to free runners: restart later (13)
6.2.x6.2.x5.1.14→ 5.26.2.x6.2.x5.1.6→ 5.25.2.x5.2.x5.1.6→ 5.22.3.x2.3.x5.1.11→ 5.25.2.x5.2.x5.1.10→ 5.29.1.x9.1.x5.1.13→ 5.22.1.x2.1.x5.1.10→ 5.24.2.x4.2.x5.1.12→ 5.23.2.x3.2.x5.1.7→ 5.21.2.x1.2.x5.1.7→ 5.22.2.x2.2.x5.1.12→ 5.21.2.x1.2.x5.1.6→ 5.24.3.x4.3.x5.1.11→ 5.2Skipped: micronaut-guides (guides site, not a library), micronaut-sourcegen (no new minor branch wanted for now).
Projects (71)
6.2.x✅6.1.05.2.05.2.0(merged)3.2.x✅3.1.05.2.05.2.0(merged)5.2.x✅5.1.15.2.05.2.0(merged)6.2.x✅6.1.05.2.0CorsSimpleRequestTest×14,SimpleRequestWithCorsNotEnabledTest×2), with 404 Not Found or a refresh count of 0: core #12880 moved these tests to a management endpoint, as for servlet and gcp. 5 are in the newExplicitHeadRouteTestfrom core #13030: theX-Handlerresponse header is missing even for a plain GET, which points to header handling in the Azure adapter. The last one,PublisherExceptionHandlerTest, was a connection reset under local load. A module-side fix task has been spawned; CI on micronaut-projects/micronaut-azure#1018 is still pending. Fix PR: micronaut-projects/micronaut-azure#1020 (function TCK suites).6.2.x✅6.1.15.1.145.2.0c6158f9e0e. 200 tests, 0 failed. Fix PRs: micronaut-projects/micronaut-cache#1064 (audit on 6.2.x) and micronaut-projects/micronaut-cache#1065 (stop publishing a strict jackson-core constraint).7.2.x✅7.1.05.2.05.2.0(merged)c6158f9e0e. 22 tests, 0 failed (on commit caa5f1d, the core 5.2 bump that micronaut-projects/micronaut-cassandra#666 re-applies on the new7.2.x).2.2.x✅2.1.05.2.05.2.0(merged)7.1.x✅7.0.15.2.05.2.0(merged)2.2.x✅2.1.05.1.125.2.0:micronaut-control-panel-ui:testand the doc example'sinspectRuntimeClasspathandplaywrightInstall. jackson-core cannot be resolved because micronaut-cache-infinispan 6.1.1 publishes{strictly 2.21.4}and micronaut-object-storage-gcp 3.1.0 publishes 2.18.9. It fails the same way in CI on micronaut-projects/micronaut-control-panel#659, and on2.2.xsince the move to cache 6.1.1 (not caused by the bump). Only cache-infinispan'sstrictlyconflicts. Fixes: micronaut-projects/micronaut-control-panel#661 against2.2.x(component metadata rule that relaxes the strict pin; jackson-core resolves to 2.22.1, 290 tests with 1 local Oracle container timeout), and root cause micronaut-projects/micronaut-cache#1065 against6.1.x(plain constraint instead ofstrictly).3.2.x✅3.1.05.2.05.2.0(merged)5.2.x✅4.14.55.1.125.2.0data-modelanddata-connectionfail to compile: Reactor 3.8 marksblock()@Nullableand NullAway treats that as an error, so data needs a fix. H2 tests (753):JdbcRepositorySpecfailed intermittently because of introspection order, fixed in #13096.5.2.x✅5.1.05.1.75.2.0c6158f9e0e. 218 tests, 15 failed, all with one cause: the Consul client tests (ConsulMockAutoRegistrationSpec×9,ConsulClientSpec,ConsulMockHealthStatusSpec,TtlHeartbeatSpec,CompositeDiscoverySpec,ClientScopeSpec) fail withInvalidFormatException: Cannot deserialize value of type java.net.InetAddress from String "<hostname>". Jackson 3.2.2, managed by core 5.2 (up from 3.1.4), no longer accepts a hostname forInetAddress. This affects Consul registration at runtime, not just tests. Baseline on core 5.1.7 (Jackson 3.1.x): 204 tests, 0 failed, so this comes from the Jackson upgrade. Fix: micronaut-projects/micronaut-discovery-client#897 (Consul addresses kept as strings; Consul tests and japiCmp pass on core 5.2.0 and 5.1.7). Update: fix micronaut-projects/micronaut-discovery-client#897 merged.2.2.x2.1.05.1.65.2.0c6158f9e0e. 108 tests, 2 failed:EclipseStoreMetricsBinderSpecandEclipseStoreMetricsBinderDisabledSpecget404 Not Foundfrom/metrics, the same regression as micronaut-sql and micronaut-kafka (released micronaut-micrometer endpoint not routed, #12960, fix in #13111). Baseline on core 5.1.6:eclipsestore21/21 with all 20 test classes selected. Update: core #13111 merged into 5.2.x (6d53fc7); bothEclipseStoreMetricsBinder*Specpass against core 5.2.x head 6d53fc7. Needs a core 5.2.1 release.6.2.x6.1.05.1.65.2.0c6158f9e0e. 15 tests, 0 failed. Fix PR: micronaut-projects/micronaut-elasticsearch#745 (audit on 6.1.x).3.3.x✅3.2.05.2.05.2.0(merged)c6158f9e0e. 284 tests, 0 failed.8.2.x✅8.1.15.2.05.2.0(merged)c6158f9e0e. 32 tests, 1 failed:test-suite-oracletimed out starting the Oracle container ("DATABASE IS READY TO USE!" never logged), an environment issue that is not core related.6.2.x✅6.1.05.2.0ErrorHandler*ones are local-load flakes. Fixed in micronaut-projects/micronaut-gcp#1538 →6.2.x(6.2.xcreated from6.1.xHEAD; the PR carries the fix, the cherry-picked bump and6.2.0-SNAPSHOT). Not core:micronaut-managementalready comes through the TCK. (1)GcpFunctionHttpServerUnderTestforcedendpoints.refresh.enabled=false, so/refreshwas 404; now a default. (2)GoogleFunctionHttpRequest.getParameters()URL-decodedmultipart/form-data, soforce=truenever bound (200, refresh count 0). That is a production bug too; form fields now come fromgetParts(), which the embedded test server andHttpFunction.invokenow provide. No TCK test excluded. Local,--rerun-tasks: TCK 235 + 246 tests on core 5.2.0 and 224 + 231 on 5.1.9, 0 failed; function module checks green.2.2.x✅2.1.05.2.05.2.0(merged)5.2.x✅5.1.05.2.05.2.0(merged)c6158f9e0e. 111 tests, 0 failed.5.2.x✅5.1.05.2.05.2.0(merged)c6158f9e0e. 22 tests, 0 failed.5.2.x5.0.15.1.65.2.0c6158f9e0e. 100 tests, 0 failed.2.2.x✅2.1.05.2.05.2.0(merged)c6158f9e0e. 35 tests, 0 failed.mastern/a5.2.x✅5.1.05.2.05.2.0(merged)c6158f9e0e. 7 tests, 3 failed:ValidatedBeanSpec(invalid bean, custom validator, custom validator that is not a bean) fails withUnexpectedTypeException: Cannot find a constraint validator for constraint: org.hibernate.validator.constraints.URL and type: class java.lang.String, raised byDefaultValidator.validateConstrainsduring bean instantiation. The project uses released micronaut-validation 5.0.0. Baseline on core 5.1.1: 7/7 pass, so this is a core regression, bisected to #12859 (aeded4f). Update: not a core patch after all. The module-side fix micronaut-projects/micronaut-hibernate-validator#598 is merged on5.1.x, and the core 5.2.0 bump micronaut-projects/micronaut-hibernate-validator#599 merged on the new5.2.xwith green CI.5.2.x✅5.1.05.2.05.2.0(merged)c6158f9e0e. 26 tests, 0 failed.1.1.x✅1.0.05.2.05.2.0(merged)c6158f9e0e. 1492 tests, 0 failed.5.2.x✅5.1.05.2.05.2.0(merged)HttpMethodMapper: theswitch (httpMethod)is not exhaustive afterHttpMethod.QUERYwas added (#12780). Adefaultbranch alone compiles, but a JAX-RS@HttpMethod("QUERY")resource then gets 405, because a custom method route is never matched for aQUERYrequest. micronaut-projects/micronaut-jaxrs#677 maps it to@Query. With it,checkpasses on 5.2.0 and matches a 5.1.12 baseline (TCK 2,764 tests, 1,074 skipped). Still needs a new5.2.xbranch for the bump.AnnotationReflectionUtils.resolveGenericToArgumentcan then move toReflectionArguments.DefaultHttpClient.setHandlerRegistryhas no public replacement:DefaultHttpClientBuilder.handlerRegistryis package-private. Update: fix micronaut-projects/micronaut-jaxrs#677 merged.5.2.x✅5.1.05.2.05.2.0(merged)c6158f9e0e. 24 tests, 0 failed.5.2.x✅5.1.05.2.05.2.0(merged)c6158f9e0e. 2 tests, 0 failed.2.3.x2.2.05.1.115.2.0c6158f9e0e. 510 tests, 0 failed.6.2.x✅6.1.05.1.75.2.0c6158f9e0e. 377 tests, 8 failed. 6 are the/metrics404 of released micronaut-micrometer 6.0.2 (KafkaListenerSpec,KafkaConsumerMetricsSpec,KafkaProducerMetricsSpec,KafkaStreamsMetricsSpec×2,KafkaStreamsMetricsDisabledSpec), caused by #12960.UncaughtExceptionsSpecfails incleanupSpec: its sharedstopContextcallsgetBeanon a context that is no longer running, which throwsIllegalStateExceptionsince #12948.KafkaClientSpec"send when Kafka is not available" gotTimeoutExceptioninstead ofExecutionException, and it fails on core 5.1.7 too. Baseline on core 5.1.7: kafka 297 tests with only that 1 failure; kafka-streams 40/40. Follow-up 2026-09-10: all 6 metrics specs pass against core with #13111 (fullcheck376 tests, 1 failed: the Groovy docsMyTest, which also fails on 5.1.7 and is fixed in micronaut-projects/micronaut-kafka#1398).UncaughtExceptionsSpec(early return instopContext) andKafkaClientSpec(a 1 sgetracing a ~1 s producer failure) are fixed in micronaut-projects/micronaut-kafka#1397. The core bump waits for a core release that includes #13111. Update: fix micronaut-projects/micronaut-kafka#1397 merged. Update: core #13111 merged into 5.2.x (6d53fc7); the metrics specs pass (0 failed) against core 5.2.x head 6d53fc7. Needs a core 5.2.1 release.5.2.x5.1.05.1.105.2.0c6158f9e0e. 89 tests, 0 failed.9.1.x9.0.05.1.135.2.0c6158f9e0e. 420 tests, 2 failed, 106 skipped (no Kubernetes cluster locally). The 2 failures (kubernetes-operatorConfigMapResourceReconcilerSpecandConfigMapResourceReconcilerWithFiltersSpec, "Failed to resolve theapiGroupfor V1ConfigMap from discovery cache") need a live cluster for API discovery, and they fail the same way on core 5.1.13 (16 tests, same 2 failures). Not core related.2.3.x2.2.05.1.105.2.07.2.x✅7.1.05.2.05.2.0(merged)c6158f9e0e. 24 tests, 0 failed.2.2.x✅2.0.15.2.05.2.0(merged)c6158f9e0e. Build and BOM check pass. The project has no test sources (test-suitecompile and test tasks areNO-SOURCE), so no tests ran.2.1.x2.0.05.1.105.2.06.1.x✅6.0.25.2.05.2.0(merged)c6158f9e0e. 506 tests. 1 flaky failure inMetricsEndpointSpec(connection reset under load) passes on rerun.6.2.x✅6.1.05.2.05.2.0(merged)c6158f9e0e. 54 tests, 0 failed.4.2.x4.1.05.1.125.2.0c6158f9e0e. 53 tests, 0 failed.6.2.x✅6.1.05.2.05.2.0(merged)c6158f9e0e. 88 tests, 0 failed.5.2.x✅5.1.05.2.05.2.0(merged)c6158f9e0e. 81 tests, 0 failed (on commit ecd5bda7, the core 5.2 bump that micronaut-projects/micronaut-nats#703 re-applies on the new5.2.x).8.2.x✅8.1.05.2.05.2.0(merged)c6158f9e0e. 3 tests, 0 failed.3.2.x3.1.05.1.75.2.0c6158f9e0e. 471 tests, 0 failed, 53 skipped (by module:object-storage-oracle-cloud24,object-storage-azure10,object-storage-aws9,object-storage-gcp8,object-storage-local2).7.3.x✅7.2.05.2.05.2.0(merged)c6158f9e0e. 1387 tests, 0 failed.1.2.x1.1.05.1.75.2.02.2.x2.1.15.1.125.2.0c6158f9e0e. 37 tests, 0 failed.6.2.x✅6.1.35.1.115.2.0c6158f9e0e.oraclecloud-function-httpfails 15/27 tests with aClassCastExceptionfrom the introspection bean class loader fallback inDefaultBeanIntrospector. Fixed by #13109 (27/27 pass with it). The other failures are OCI config or pre-existing. Update: core #13109 is merged into 5.2.x (1154498);:micronaut-oraclecloud-function-http:testpasses 27/27 (1@PendingFeatureskipped) against core 5.2.x head 1d17e8f. Needs a core 5.2.1 release.6.2.x✅6.1.05.2.05.2.0(merged)c6158f9e0e. 25 tests, 0 failed.5.1.x✅5.0.05.1.3c6158f9e0e. 25 tests, 1 failed:DataLeakageOverrideSpecoverridesshouldIncludeErrorMessageAsDetailForDefaultProblemand expects the detail "Internal Server Error: foo data", but gets "Internal Server Error". Core 05421f2 no longer includes the exception message in the error message by default (micronaut.server.error-response-include-message=never) and exposes it asErrorContext.getExceptionMessage(), so micronaut-problem should build the detail from that. Fix: micronaut-problem-json#568 (27 tests pass on core 5.1.3 and 5.2.0; no other 5.2-only failures). Update: fix micronaut-projects/micronaut-problem-json#568 merged.1.2.x1.1.05.1.65.2.03.2.x3.1.05.1.65.2.0c6158f9e0e. 21 tests, 0 failed.7.2.x✅7.0.25.2.05.2.0(merged)c6158f9e0e. 44 tests, 0 failed.5.2.x5.1.05.1.115.2.0c6158f9e0e. 97 tests, 1 failed: Kotlin docs exampleHeadersSpecthrowsRabbitClientException: The @RabbitHeaders annotation is applied to an argument that is not java.util.Map<String, ?>.ProductClient.send(@RabbitHeaders headers: Map<String, Any>)compiles toMap<String, ? extends Object>, which is now aWildcardArgument(#13023).DefaultArgument.equalsTypecompares nested type parameters withequals, andDefaultWildcardArgument.equalsrequires the other side to be a wildcard too, soargument.equalsType(Argument.mapOf(String.class, Object.class))is false. It passes on core 5.1.11 (HeadersSpec1/1 with Predictive Test Selection disabled). Core regression. Fix: #13115 (not fixed by #13109/#13111/#13114; control retest still fails). Update: core#13115 merged into 5.2.x (fc92af4).4.3.x✅4.2.05.2.05.2.0(merged)c6158f9e0e. 26 tests, 0 failed.7.2.x✅7.1.05.2.05.2.0(merged)5.2.x✅5.1.05.1.135.2.0c6158f9e0e. 80 tests, 0 failed.4.2.x✅4.1.05.2.05.2.0(merged)c6158f9e0e. 10 tests, 0 failed.5.4.x✅5.3.25.2.05.2.0(merged)c6158f9e0e. 1675 tests.BuiltInEndpointsSpec(sensitive endpoint without aSensitiveEndpointRulereplacement) fails every time: the 500 response no longer includes the exception message, because core 05421f2 addedmicronaut.server.error-response-include-messagewith defaultnever. The test needs updating.SecuredExpressionSpecwas flaky and passes on rerun. Update: fix micronaut-projects/micronaut-security#2277 merged.3.2.x3.1.15.1.35.2.0@JsonIgnorePropertiesinheritance regression, fixed in #13099. 6 failures intest-suite-tck-jackson-databindcome from Jackson 3.1.4 → 3.2.2. With micronaut-projects/micronaut-serialization#1415:checkpasses on 5.2.xc6158f9e0e(0 failures). On 5.2.0 only theSerdeJsonIgnoreAllowSpecinheritance case fails, fixed in 5.2.1 by #13099.test-suite-http-server-tck-nettyis flaky locally (connection closed, a different test each run).6.2.x6.1.05.1.35.2.0c6158f9e0e. 1883 tests, 34 failed, all module-side. 28 are 7CorsSimpleRequestTesttests × the Tomcat, Undertow, JDK and POJA-Apache TCK suites (refresh count 0): #12880 made the CORS TCK call the management/refreshendpoint, and servlet's TCK suites lackmicronaut-management. 4 are the Jetty, Tomcat and Undertow*ErrorSpecstreaming error tests and JettyFilterErrorSpec, which expect the exception message that core 05421f2 now hides by default (micronaut.server.error-response-include-message=never). 2 are POJA-ApacheSimpleRequestWithCorsNotEnabledTest404s with the same cause: #12880 rewrote that test to call/refreshtoo. Baseline on core 5.1.3: all 34 of these pass.5.2.x✅5.1.05.2.05.2.0(merged)c6158f9e0e. 36 tests, 0 failed, but:micronaut-docs-examples:micronaut-example-kotlin:compileTestKotlinfails:ShoppingControllerTest.ktcalls.body()and.header()onFlux...blockFirst(), which Reactor 3.8 (managed by core 5.2) marks@Nullable, so Kotlin types itHttpResponse<Cart>?. The docs example needs!!or safe calls. Same Reactor 3.8 nullability cause as micronaut-data; no core API change. It compiles on core 5.1.10 (Reactor 3.7). Update: session#381 is merged; Renovate rebased micronaut-projects/micronaut-session#380 onto it andbuild (25)now passes.build_matrixfailed on an HTTP 500 from services.gradle.org and is being rerun.2.2.x2.2.05.1.10c6158f9e0e. 1550 tests, 1 failed:test-suite-kotlinHeronTestassertsgetAnnotationValuesByType(Heron.Boo)returns 1, but core 5.2 returns 2. The test comment already says "There should actually be 2 Boo annotations", so this is core fixing repeatable annotation resolution. The test should expect 2 and re-enable thebamassertion. Baseline on core 5.1.10:test-suite-kotlin68/68, so the change comes from core 5.2.6.2.x✅6.1.05.2.05.2.0(merged)c6158f9e0e. 66 tests, 0 failed.7.2.x✅7.1.25.1.135.2.0c6158f9e0e. 446 tests, 68 failed: everyDataSourcePoolMetadataSpecfeature injdbc-hikari(32),jdbc-tomcat,jdbc-dbcpandjdbc-ucp(12 each) gets404 Not Foundfrom the/metricsendpoint of released micronaut-micrometer 6.0.2. The same modules pass on core 5.1.13. This is a core regression: bisected to #12960 (d44e268). Update: core #13111 merged into 5.2.x (6d53fc7); thejdbc-hikari/-tomcat/-dbcp/-ucppool metadata specs pass (47 tests, 0 failed) against core 5.2.x head 6d53fc7. Needs a core 5.2.1 release.5.2.x✅5.1.15.2.05.2.0(merged)c6158f9e0e. 261 tests, 0 failed.4.3.x4.2.05.1.115.2.0TestResourcesClientTest"reasonable error message" gets "Internal Server Error" instead of the server's message, because core 05421f2 setsmicronaut.server.error-response-include-messagetonever. This also hides test resources service errors from users; a module-side fix task has been spawned. The other 11 are local environment problems: 8 Oracle XE and MongoDB container start timeouts, 2IntellijIdeaDatasourceExporterStandaloneProjectTestnested builds that cannot see the local core snapshot, and 1 macOSBindExceptionin the H2 loopback test. Fix PR: micronaut-projects/micronaut-test-resources#1212.3.2.x✅3.1.05.2.05.2.0(merged)c6158f9e0e. 1152 tests, 0 failed.8.3.x✅8.2.05.1.75.2.0c6158f9e0e. 185 tests, 0 failed.:micronaut-tracing-bom:checkBomfails on the third-partyopentelemetry-instrumentation-bom2.30.0 (it declaresopentelemetry-semconvfrom another group and imports another BOM). Not core related; suppress it inmicronautBomor align OpenTelemetry.5.2.x✅5.1.05.1.115.2.0c6158f9e0e. 932 tests, 33 failed. 32 are Jakarta Validation TCK failures (constraint inheritance, group sequence inheritance, cross-parameter and generic validator resolution, property paths,ConstraintValidatorContext); the same TCK passes 384/384 on core 5.1.11, so this is a core regression, bisected to #12977 (2c9161c, add the micronaut-reflection module). Fixed by #13114: the TCK passes 384/384 on 5.2.x + #13109/#13111/#13114. The other isValidatorSpec"@introspected is required to validate the bean", a known 5.2 behaviour change (500/500 on 5.1.11). Update: core #13114 merged into 5.2.x (9089b06); the Jakarta Validation TCK passes 384/384 against core 5.2.x head fc92af4. Needs a core 5.2.1 release.6.3.x✅6.2.05.2.05.2.0(merged)c6158f9e0e. 587 tests, 2 failed.FreemarkerViewRendererSpecexpects "Internal Server Error: View [bogus] does not exist", which core 05421f2 now hides by default (micronaut.server.error-response-include-message=never), so the test needs updating.TurboFrameSpec"/frame/disabled" hit a connection reset under load; it is flaky and passes 26/26 on 3 reruns. Baseline on core 5.1.7: views-freemarker 13/13 and views-turbo 99/99.The core version on each branch comes from
micronautingradle/libs.versions.tomlon the default branch. The bump PR is the open Renovate "Update Micronaut dependencies" PR and the core version it targets.