The GitHub Actions job "CI - Groovy Joint Validation Build" on grails-core.git/ci/gradle-cache-writer-by-major has succeeded. Run started by GitHub user jdaugherty (triggered by jdaugherty).
Head commit for run: d277b7f7e1dd0b51b9b5e63766a2f1ce755ed77f / James Daugherty <[email protected]> Write the Gradle cache only from the default branch's major and later The core build's flagged matrix entries wrote the Gradle User Home on every release branch. A run can restore entries only from its own branch and the default branch, so the 7.x branches each kept a near-identical copy that no other branch could read, while the 8.x and 9.x lines, which diverge from each other, were the ones worth caching. A step now decides whether the entry saves. It writes only on a push or dispatch, only on a branch whose major version is at least the default branch's, and, for Windows and macOS, only on that major's first branch. Today that makes 7.x read-only, Linux write on every 8.x and 9.x branch, and Windows and macOS write on 8.0.x and 9.0.x. macOS is now a flagged writer as well. The rule is relative to the default branch, so promoting 9.0.x later stops 8.x writing without any edit, and any unexpected input leaves the cache read-only. The read-only jobs' comments point at it. Report URL: https://github.com/apache/grails-core/actions/runs/38628926613 With regards, GitHub Actions via GitBox
