The GitHub Actions job "Code Style" on grails-core.git/ci/policy-follow-ups has failed. Run started by GitHub user matrei (triggered by matrei).
Head commit for run: 08d81a029655594f4af0d9bedb17c44afd3e4e9e / Mattias Reichel <[email protected]> Publish nothing of a CI run cancelled before its builds finish, and correct the CI policy docs Follow-up to #16673. publishGradle needed only buildGradle, so on any push run a cancel more than a few minutes in still published the superseded commit's Gradle plugins, and on a run without tests also its core and docs but not its Forge, which was still building. 8.0.x run 39638916842 shows the first case: its plugins went out at 17:13 and a newer push cancelled the run at 17:26, before its tests finished. publishGradle now also waits for buildForge and validateDependencies, so a cancel before the builds finish publishes nothing of that commit, and a commit whose Forge build or dependency validation failed is no longer published. A cancel after the builds publishes the whole chain on a run without tests, and only the Gradle plugins while tests are still running; the comments in gradle.yml and the CI policy section of AGENTS.md now say that instead of claiming that a cancelled commit is never published. AGENTS.md also no longer lists the snapshot publish among the jobs that run on pull requests, and names force-cancel for a publish that a normal cancel cannot stop. CONTRIBUTING.md no longer says every push to a branch cancels the run in flight, which only CI and the Groovy joint build do. RELEASE.md notes that a merge cancels the manual test run of the release branch, since both share a concurrency group. Report URL: https://github.com/apache/grails-core/actions/runs/39753143366 With regards, GitHub Actions via GitBox
