a very stupid question: do I understand correctly there will be no more 7.0.X versions in the future and the path to go is from 7.0.10 to 7.1.0?

If needed there will be more 7.0.x versions.

I see. What I'm trying to understand is if today is worth updating our project from 7.0.10 to 7.1.0.

I would say that if there is no feature in 7.1.x that you want, you can stay on 7.0.x and jump directly to 8.0.x when it is released.

I'd prefer not to make to long jumps but that a team decision so I just what to pass correct information to all of them to make a good decision.

what about security fixes? I'm thinking of the dependencies of Grails can they lead to a new 7.0.x? At the moment we have this in our

gradle.properties

# Workaround CVE-2026-34483_CVE-2026-34486_CVE-2026-34487
# Remove when a new version of Grails upgrade Tomcat
tomcat.version=10.1.54

but we would prefer to have no special pinning

we are patching both 7.x versions as long as spring boot is updating

Hey I'm having a breaking change between 7.1 and 7.0. I'm probably doing something dumb here, but in 7.1, our unit tests are failing because it can't find our datastores. For context, our app uses multiple datastores. There's a collection of exceptions that all go like one of these:

No datastore found for connection named [SomeDataStore]
org.grails.datastore.mapping.core.exceptions.ConfigurationException: No datastore found for connection named [mag]
	at org.grails.datastore.mapping.simple.SimpleMapDatastore.getDatastoreForConnection(SimpleMapDatastore.java:362)
	at com.platform.project.service.SomeDataServiceSpec.test list returns all SomeDataStoreUsers(SomeDataServiceSpec.groovy:44)

@User can you try to generate an app and config the datastores the same way? see if you can reproduce it