Given this does not impact a default generated app: https://github.com/jamesfredley/controller-groovy-cast-exception/blob/working/grails-app/controllers/com/example/ContestController.groovy and we do not know the URLMappings line or combination of lines that results in this scenario, the bug is limited in scope, but is a regression from 6.2.3 and prior 7 RCs and milestones for some specific case.
If we release 7.0.0 today, it was scheduled to go out last night, we could finish the review on https://github.com/apache/grails-core/pull/15153 make a decision on Groovy 4.0.29 and start a vote on 7.0.1. On 2025/10/19 12:18:29 Søren Berg Glasius wrote: > If our test applications works, and if there is no application that can > prove this error, I believe it can wait for 7.0.1. Stopping the vote for > 7.0.0 is wasting a lot of time to get the first GA out the door. > > Den søn. 19. okt. 2025 kl. 04.12 skrev James Fredley < > [email protected]>: > > > Additionally Groovy 4.0.29 has been released, but Spring Boot Dependencies > > is still on 4.0.28. If we cancel 7.0.0 vote and restart vote, do we want > > to move forward with Groovy 4.0.29, before Spring Boot 3.5.7 is released? > > > > On 2025/10/19 02:08:15 James Fredley wrote: > > > This is not occurring in a basic application: > > https://github.com/jamesfredley/controller-groovy-cast-exception/blob/working/grails-app/controllers/com/example/ContestController.groovy > > > > > > But is occurring in one with more complex URLMappings, although we do > > not have a shared example. > > > > > > https://github.com/apache/grails-core/pull/15153 resolves > > https://github.com/apache/grails-core/issues/15147 in the more complex > > application. > > > > > > Now the question, do we proceed with 7.0.0 or cancel and restart the > > vote with this fixed? If we cancel it will also mean restarting votes on > > spring-security, redis and quartz. > > > > > > On 2025/10/18 21:29:36 Scott Murphy Heiberg wrote: > > > > -1 After thoroughly testing an encountering a major bug with > > controller method binding > > > > https://github.com/apache/grails-core/issues/15147 > > > > > > > > On 2025/10/15 23:51:47 James Daugherty wrote: > > > > > Hi Everyone, > > > > > > > > > > I am happy to start the VOTE thread for an Apache Grails release of > > > > > version 7.0.0! > > > > > > > > > > Please note the following build reproducibility issues for this > > release: > > > > > 1. grails-forge-core-7.0.0-javadoc.jar # due to groovy 3 in forge, we > > > > > need to update to groovy 4 to fix this > > > > > > > > > > Given that these differences are known, explainable, and immaterial, > > > > > we are moving forward with a release vote. > > > > > > > > > > > > > > > Pre-release discussion thread is here: > > > > > https://lists.apache.org/thread/0d7zdol8br0co2wj7v7vbbz26oz18d3m > > > > > > > > > > Release notes for the release are here: > > > > > https://github.com/apache/grails-core/releases/tag/v7.0.0 > > > > > > > > > > The tag for this release is: > > > > > https://github.com/apache/grails-core/releases/tag/v7.0.0 > > > > > Tag commit id: abd605eda3dcb5dcbd80698be462cf9ca9a52875 > > > > > > > > > > The artifacts to be voted on are located as follows (r80093): > > > > > Source release: > > https://dist.apache.org/repos/dist/dev/grails/core/7.0.0/sources > > > > > Binary distributions: > > > > > > > https://dist.apache.org/repos/dist/dev/grails/core/7.0.0/distribution > > > > > > > > > > Release artifacts are signed with a key from the following file: > > > > > https://dist.apache.org/repos/dist/release/grails/KEYS > > > > > > > > > > Please vote on releasing this package as: Apache Grails 7.0.0. > > > > > > > > > > Reminder on ASF release approval requirements for PMC members: > > > > > https://www.apache.org/legal/release-policy.html#release-approval > > > > > > > > > > Hints on validating checksums/signatures (but replace md5sum with > > sha512sum): > > > > > https://www.apache.org/info/verification.html > > > > > > > > > > Details of our release process are documented at: > > > > > https://github.com/apache/grails-core/blob/HEAD/RELEASE.md > > > > > > > > > > As a reminder, most of our tools support an env `GRAILS_REPO_URL` so > > > > > that the tools can be used from the staging location. Set it to the > > > > > staging repo like this: `export > > > > > GRAILS_REPO_URL= > > https://repository.apache.org/content/groups/staging` > > <https://repository.apache.org/content/groups/staging> > > > > > > > > > > The vote is open for a minimum of 72 hours and passes if a majority > > of at least > > > > > three +1 PMC votes are cast. > > > > > > > > > > [ ] +1 Release Apache Grails 7.0.0 > > > > > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > > > > > [ ] -1 Do not release Apache Grails 7.0.0 because... > > > > > > > > > > Here is my vote: > > > > > > > > > > +1 (binding) > > > > > > > > > > > > > > > > > -- > > Med venlig hilsen, > Søren Berg Glasius > > Hedevej 1, Gl. Rye, 8680 Ry > Mobile: +45 40 44 91 88 > --- Press ESC once to quit - twice to save the changes. >
