feat(deps): Bump Micronaut platform to 5.0.0 (GA)#3
Closed
jamesfredley wants to merge 1 commit into
Closed
Conversation
Micronaut Platform 5.0.0 shipped on Maven Central (io.micronaut.platform:micronaut-platform:5.0.0). Replace the 5.0.0-M2 milestone we were tracking with the released GA. Accompanying alignments required to keep validateDependencyVersions green: - dependencies.gradle: bump the grails-micronaut-bom Groovy override from 5.0.5 to 5.0.6 so the strict pin matches Micronaut 5 GA's managed groovy.version. spock stays at 2.4-groovy-5.0 (unchanged in GA). - grails-bom/micronaut/build.gradle: refresh the comment on the tools.jackson exclude. Micronaut 5.0.0 ships jackson-bom 3.1.3 while Spring Boot 4.0.6 ships 3.1.2 - the two platforms still disagree on the patch, but the direction is now reversed (Micronaut ahead of Spring Boot rather than behind). The exclude itself stays in place so spring-boot-dependencies remains the single source of truth for Jackson 3. This is the first commit of a draft PR; more fallout is expected as downstream modules pick up the new platform. Assisted-by: claude-code:claude-opus-4-7
Owner
Author
|
Superseded by apache#15677 (same commits, apache-hosted branches, stacked on apache#15676). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Draft - stacked on top of apache#15675. This PR uses the Spring Boot 4.0.6 branch (
deps/spring-boot-4.0.6) as its base so the dependency-version fallout from that bump does not muddy this one.Bumps
micronautPlatformVersionfrom5.0.0-M2to5.0.0(GA, published to Maven Central on 2026-05-20).Release notes / changelog: https://github.com/micronaut-projects/micronaut-platform/releases/tag/v5.0.0
Maven Central: https://repo1.maven.org/maven2/io/micronaut/platform/micronaut-platform/5.0.0/
What's in this first commit
The minimum change set that keeps
validateDependencyVersionsgreen after the bump:gradle.properties:micronautPlatformVersion=5.0.0-M2->5.0.0.dependencies.gradle: bump thegrails-micronaut-bomGroovy override from5.0.5to5.0.6so our strict pin matches Micronaut 5 GA's managedgroovy.version. Spock stays at2.4-groovy-5.0(unchanged in GA).grails-bom/micronaut/build.gradle: refresh the comment on thetools.jacksonexclude. Micronaut 5.0.0 shipsjackson-bom 3.1.3while Spring Boot 4.0.6 ships3.1.2- the platforms still disagree on the patch, just in the opposite direction now. The exclude itself stays in place sospring-boot-dependenciesremains the single source of truth for Jackson 3.Notable upstream version moves (5.0.0-M2 -> 5.0.0)
Read directly from the published
micronaut-platform-5.0.0.pom:micronaut.core.version5.0.0-M235.0.0micronaut.data.version5.0.0-M55.0.1micronaut.serde.version3.0.0-M73.0.0micronaut.mongo.version/micronaut.mongodb.version6.0.1-M16.0.1micronaut.langchain4j.version2.0.0-M12.0.0jackson.version3.1.03.1.3groovy.version5.0.45.0.6spock.version2.4-groovy-5.02.4-groovy-5.0spring.boot.version4.0.34.0.6(matches our pin)spring.version7.0.67.0.7Known platform-level breaking changes
From the v5.0.0 release notes - flagged here so reviewers know what to watch for in subsequent commits:
io.reactivex:rxjavaandio.micronaut.rxjava2:*are no longer managed by the platform. OurmicronautRxjava2Version=2.9.0ingradle.propertiesis already floated outside the BOM (comment: "micronaut libraries not in the bom due to the potential for spring mismatches"), so the existing pin still works - but consumers should be aware.micronaut.eclipsestore.version=2.0.0).jaxrs.api.version3.1.0 -> 4.0.0 (Jakarta RESTful Web Services 4).kafka.version3.9.1 -> 4.2.0 - major Kafka client jump.None of these affect anything
grails-corecurrently consumes, but they are landmines for downstream Grails-on-Micronaut apps.What is NOT addressed yet
This PR intentionally ships the minimum-viable bump first. Expect follow-up commits for:
grails-micronaut,grails-test-examples/micronaut*, andgrails-test-examples/plugins/micronaut-singleton.micronautSerdeJacksonVersion=2.11.0ingradle.propertiesis still on the Micronaut Serde 2.x line while Micronaut 5 GA ships Serde 3.0.0. It is intentionally floated outside the BOM today; whether to bump it is a separate decision pending what the graphql test examples actually need.micronautRxjava2Version=2.9.0- same situation; out-of-band pin, likely fine but worth confirming.grails-forgestays onmicronautVersion=4.10.10(the Forge IS a Micronaut 4.x app, per the comment atgrails-forge/gradle.properties:27). Out of scope for this PR.Verification so far:
Full build / test execution is the next step and likely the source of most of the remaining work on this branch.