The GitHub Actions job "CI" on grails-core.git/ci/release-drafter-pr-concurrency has succeeded. Run started by GitHub user jdaugherty (triggered by jdaugherty).
Head commit for run: 52bc48a124852a4cfa9987f305ddecdf0a84aa5b / James Daugherty <[email protected]> Hold the release drafter off while a release of the branch is in progress The drafter and the release pipeline can touch the same release object. The drafter updates whichever draft targets its branch, and the release being released is briefly a draft again while pre-release moves its tag, so a drafter run in that window rewrites the release's tag, name and body. Sharing a concurrency group with the pipeline was tried for this and undone: the pipeline waits at approval gates for days, and every push queued the drafter behind it. So the drafter now skips instead. Its first step lists the runs of release.yml and release-close.yml, maps a release run's head ref - the tag - to the branch it was cut from, and if any run for this branch is not completed, including one waiting at a gate, the draft is left exactly as it was. Nothing useful is lost: the next version is not known until the close has merged back, and the first push after the pipeline completes brings the draft up to date. If the runs cannot be listed, the drafter holds off and warns rather than guess. The seed and drafter steps are conditional on the guard, the verify step reports a hold as a hold rather than as a missing draft, and the job asks for actions: read to list the runs. Report URL: https://github.com/apache/grails-core/actions/runs/36822568799 With regards, GitHub Actions via GitBox
