The GitHub Actions job "CI" on grails-core.git/feat/gradle-managed-version-overrides has failed. Run started by GitHub user jamesfredley (triggered by jamesfredley).
Head commit for run: 179ae7d39b8ae1ec5e46389dddee839b76a76eb5 / James Fredley <[email protected]> fix: ignore documentation configuration when detecting the project BOM GrailsDependencyValidatorPlugin.detectBomPath scanned every configuration and failed when a project declared more than one Grails BOM. The shared gradle/docs-dependencies.gradle script wires platform(grails-bom) onto the documentation configuration purely to resolve groovydoc tooling versions, so any module that selects a non-default BOM variant for its real dependencies (grails-micronaut, grails-data-hibernate5/7/*) declared two BOMs and tripped the validator's exactly-one-BOM guard, breaking the "Validate Dependency Versions" CI job. Exclude the doc-tooling documentation configuration from BOM detection so the variant BOM a project selects for its real dependencies is the one detected. Layering two BOMs on actual dependency configurations still fails, preserving the guard's intent. Add GrailsDependencyValidatorPluginSpec covering the documentation-config exclusion, the docs-only case, the single-BOM and no-BOM cases, and the genuine double-BOM throw. Assisted-by: claude-code:claude-4.8-opus Report URL: https://github.com/apache/grails-core/actions/runs/27312183132 With regards, GitHub Actions via GitBox
