The GitHub Actions job "CI" on grails-core.git/fix/sitemesh-stale-snapshot-bom has succeeded. Run started by GitHub user borinquenkid (triggered by borinquenkid).
Head commit for run: fc2100a5f1878490058672c7f0bae0654a2870cb / Walter Duque de Estrada <[email protected]> fix: prevent stale published grails-bom snapshot from downgrading sitemesh The gsp-spring-boot test app imports grails-bom via io.spring.dependency-management, which downloads the PUBLISHED snapshot from Nexus rather than the local project. When a CI run publishes the BOM before the sitemesh version bump lands (or when a prior run publishes with the old version), the managed-version rule applies 3.2.2 — a version that has never been published for the spring-webmvc-sitemesh standalone artifact, which only exists starting at 3.3.0-M1. This creates a circular deadlock: build fails → publish skipped → stale BOM stays on Nexus → next build fails. Fix: add a resolutionStrategy.eachDependency rule in functional-test-config.gradle that reads sitemesh version keys from the local grails-bom project ext (set after evaluationDependsOn completes) and applies them. Because eachDependency rules are applied in registration order and this rule is registered after the spring plugin's rule, it takes precedence (last useVersion wins). Co-Authored-By: Claude Sonnet 4.6 <[email protected]> Report URL: https://github.com/apache/grails-core/actions/runs/28184722445 With regards, GitHub Actions via GitBox
