The GitHub Actions job "CI" on grails-core.git/deps/grails-bom-inherit-spring-managed has succeeded. Run started by GitHub user jamesfredley (triggered by jamesfredley).
Head commit for run: eb78d1b612a4988d3007effede450be22d35fbec / James Fredley <[email protected]> Inherit Spring Boot managed dependency versions in grails-bom Remove version pins from the root dependencies.gradle that duplicate versions already managed by the spring-boot-dependencies BOM (Spring Boot 4.1.0). Where our pin equals Spring Boot's managed version it is dead weight that only blocks free patch and security updates when Spring Boot bumps the dependency, so it is removed and inherited from Spring Boot. Removed (each equal to Spring Boot 4.1.0's managed version): - byte-buddy 1.18.10 (and byte-buddy-agent) - commons-codec 1.21.0 - commons-lang3 3.20.0 - jakarta.servlet-api 6.1.0 - jakarta.validation-api 3.1.1 - junit / junit-jupiter 6.0.3 (the 12 junit-* entries plus the redundant junit-bom platform import; Spring Boot already imports junit-bom:6.0.3) - mongodb 5.8.0 (bson, mongodb-driver-core, mongodb-driver-sync, bson-record-codec) - rxjava3 3.1.12 Also drop the jakarta.servlet/jakarta.validation excludes from grails-bom/base/build.gradle. They only existed to win a since-resolved selenium-versus-Spring-Boot conflict; both versions now match Spring Boot, so its platform can manage them. Kept intentionally: graphql-java 25.0 is retained as a deliberate drift tripwire (graphql-java-extended-scalars is not managed by Spring Boot and must move in lockstep), with a rationale comment added; groovy 4.0.32 and selenium 4.38.0 remain intentionally divergent; spring-retry stays because Spring Boot 4 dropped its management. The legacy grails-shell-cli derives its own dependency management by parsing the published grails-bom POM and previously skipped third-party imports such as spring-boot-dependencies. Teach GrailsDependencyVersions to also follow third-party imported BOMs, with cycle protection and first-writer-wins precedence so Grails' own pinned versions still win, so the CLI keeps surfacing the versions now inherited from Spring Boot. Verified by regenerating the grails-bom and grails-base-bom POMs (only the removed constraints disappear; the Spring Boot import remains), confirming every affected module resolves the removed dependencies to Spring Boot's identical versions, and running validateDependencyVersions across all modules. Fixes #15674 Assisted-by: claude-code:claude-opus-4-8 Report URL: https://github.com/apache/grails-core/actions/runs/27356938592 With regards, GitHub Actions via GitBox
