The GitHub Actions job "Build Health" on grails-core.git/fix/custom-id-generator-metadata has failed. Run started by GitHub user jdaugherty (triggered by jdaugherty).
Head commit for run: f15d4688ddc75742032b034c923c27716e314e1a / James Daugherty <[email protected]> Preserve custom identifier generators in mapping metadata Since c74f868890 the default identity mapping resolved the generator name through ValueGenerator.valueOf while the mapping was built, so any name that is not a built-in constant, such as a Hibernate generator class name, failed entity registration with "No enum constant ValueGenerator.<NAME>". Grails 7 resolved the name lazily and nothing on the simple map or Mongo path read it, so unit tests that mock such a domain class with DataTest broke on upgrade. A name that is not a built-in constant now resolves to ValueGenerator.CUSTOM and stays on the mapped form for the datastore to interpret, which is what the Hibernate and Neo4j mapping factories already did for themselves. The Neo4j override is removed because the base behaviour now matches it. The unit testing guide notes that a mocked domain class never runs such a generator. Report URL: https://github.com/apache/grails-core/actions/runs/36959163779 With regards, GitHub Actions via GitBox
