The GitHub Actions job "CI - Groovy Joint Validation Build" on 
grails-core.git/fix/15613-isolate-micronaut-from-joint-build has failed.
Run started by GitHub user jamesfredley (triggered by jamesfredley).

Head commit for run:
71c8abf6ea0ee9fab7f7fa07788e39de3ba2e7c1 / James Fredley 
<[email protected]>
fix(ci): exclude Grails-Micronaut island from Groovy joint validation build

The Joint Validation Build's "Swap Groovy Version" step rewrites every
'groovy.version' line in dependencies.gradle to point at the locally built
apache/groovy 4.x snapshot - including the override inside the
grails-micronaut-bom block. That BOM still pins Spock to 2.4-groovy-5.0
(intentionally, to match the Micronaut platform's Groovy 5 baseline),
which fails Spock's compile-time Groovy major-version check and breaks
every Spock spec in the test-examples that consume :grails-micronaut-bom.

Rather than spread Spock's iKnowWhatImDoing.disableGroovyVersionCheck
escape hatch across the framework build, keep Micronaut on its own
dependency island: gate :grails-micronaut, :grails-micronaut-bom, and
the five Micronaut-tied test-examples in settings.gradle behind a
new -PskipMicronautTests project property, and pass that property in
groovy-joint-workflow.yml so the Groovy 4 snapshot matrix never tries
to evaluate the Groovy-5-pinned subgraph. The flag is a no-op locally
and in the regular gradle.yml CI run; only the joint validation build
opts in.

Fixes #15613

Assisted-by: claude-code:claude-opus-4-7

Report URL: https://github.com/apache/grails-core/actions/runs/25197521036

With regards,
GitHub Actions via GitBox

Reply via email to