jamesfredley opened a new pull request, #15704:
URL: https://github.com/apache/grails-core/pull/15704

   ## Summary
   
   Bumps Spring Boot from `4.0.6` to `4.1.0-RC1` (released to Maven Central).
   
   The change is two lines in `dependencies.gradle`:
   
   - `spring-boot.version`: `4.0.6` -> `4.1.0-RC1`
   - `mongodb.version`: `5.6.5` -> `5.7.0-beta1`
   
   The MongoDB driver bump is required: the Spring Boot 4.1.0-RC1 dependency 
BOM now manages `org.mongodb` at `5.7.0-beta1`, so `validateDependencyVersions` 
fails unless Grails' pin is aligned to match. This mirrors the prior alignment 
done when Spring Boot was bumped to 4.0.6 (commit `5d454365ae`, "Align 
mongodb.version with Spring Boot 4.0.6 (5.6.5)").
   
   ## Local verification
   
   Ran the equivalent of the CI jobs against this change (JDK 21):
   
   - `validateDependencyVersions` (root + `grails-gradle`): PASS
   - `./gradlew build :grails-shell-cli:installDist groovydoc -PonlyCoreTests`: 
BUILD SUCCESSFUL
   - `grails-gradle` build (compiles/tests against 
`spring-boot-gradle-plugin:4.1.0-RC1`): BUILD SUCCESSFUL
   - Functional tests (`-PonlyFunctionalTests`): all specs pass on Spring Boot 
4.1.0-RC1 (app banner confirms the running version). The only local failures 
were environmental and were confirmed not to be regressions:
     - 3 `hyphenated.*ControllerSpec` failed with "Could not find a valid 
Docker environment" (Testcontainers/Geb) because no Docker daemon was running 
locally; these run on the CI Linux runners.
     - 2 GORM/datasource specs flaked due to shared in-memory DB pollution 
under local parallel execution; both pass cleanly when the modules are run in 
isolation.
   
   The remaining CI matrix (Hibernate 5 functional, MongoDB functional, Forge, 
and the Java 17/21/25 x Linux/macOS/Windows combinations) runs automatically on 
this PR.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to