The GitHub Actions job "CI - Groovy Joint Validation Build" on grails-core.git/feat/gradle-managed-version-overrides has failed. Run started by GitHub user jamesfredley (triggered by jamesfredley).
Head commit for run: 931a54b54a56b94c0b7e4473dffcdd95bdd6d454 / James Fredley <[email protected]> docs: document Spring DM removal in Grails 8 upgrade guide Add section 14 "Spring Dependency Management Plugin Replaced by Gradle Platforms" to the upgrading-to-8.0.x guide, covering: - The plugin is no longer applied; Grails Gradle Plugin uses native platform(grails-bom) instead, and bom-property-overrides preserves the gradle.properties / ext['...'] override workflow. - No action required for most apps - existing override forms keep working identically. - The two Spring DM features with no automatic migration: 1. dependencyManagement { dependencies { dependency 'g:a:v' } } DSL for arbitrary non-BOM pins - migrate to direct dependencies { implementation } or resolutionStrategy.force. 2. Version-range strings inside BOM <properties> values - now pass through to Gradle's native useVersion() rather than Spring DM's resolver. Zero impact on the Grails / Spring Boot BOM chain; only relevant for custom BOMs. - Conflict-resolution behavioural difference: Spring DM forced BOM versions unconditionally; Gradle platform() participates in standard highest-version-wins resolution. enforcedPlatform() is the migration path for "BOM wins always" semantics. Sections 15-23 renumbered to make room. Two pre-existing heading-level typos in former 21/22 (===== instead of ====, missing period after 22) fixed in passing. Report URL: https://github.com/apache/grails-core/actions/runs/26256351912 With regards, GitHub Actions via GitBox
