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

   Updates the managed Groovy version from 5.1.2 to 5.1.3.
   
   [Groovy 5.1.3](https://groovy-lang.org/changelogs/changelog-5.1.3.html) is a 
three-fix release, all bugs, no new features or API changes:
   
   - GROOVY-12413 – `TYPE_USE` annotations on primitive record components and 
tuple-constructor parameters are duplicated or misapplied
   - GROOVY-12415 – decompiler crashes on a `TYPE_USE` annotation on a 
primitive Java record component
   - GROOVY-12416 – `SecureASTCustomizer` indirect import check does not box 
primitive receiver types
   
   Nothing else moves: every `org.apache.groovy` module POM declares the same 
third-party dependencies at the same versions as 5.1.2 (the full set was 
diffed), so `jline.version` stays at 3.30.16 and no other BOM entry needs to 
follow.
   
   Verified locally:
   
   - `./gradlew validateDependencyVersions` passes
   - `./gradlew build -PskipTests -x javadocJar` passes for every module 
(`javadocJar` on `grails-gsp-spring-boot` fails identically on unmodified 
`8.0.x` because groovydoc and javadoc both emit `help-doc.html`; it is 
unrelated to this change)
   - test suites pass with no failures in `grails-bootstrap` (145), 
`grails-spring` (3), `grails-core` (654), `grails-web-common` (92), 
`grails-databinding` (33), `grails-validation` (91), `grails-domain-class` (5), 
`grails-url-mappings` (19), `grails-controllers` (89), 
`grails-testing-support-core` (9), `grails-gsp` (666), `grails-gsp-core` (239), 
`grails-web-gsp` (19), `grails-taglib` (54), `grails-web-taglib` (77), 
`grails-layout` (16), `grails-sitemesh3` (86) and `grails-gsp-spring-boot` (30) 
— 2,327 tests in the modules most exposed to a compiler change; the remaining 
modules rely on CI
   


-- 
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