Skip to content

docs: document the required release concurrency block#5

Merged
sebhoss merged 1 commit into
mainfrom
docs/release-concurrency-note
Jun 21, 2026
Merged

docs: document the required release concurrency block#5
sebhoss merged 1 commit into
mainfrom
docs/release-concurrency-note

Conversation

@sebhoss

@sebhoss sebhoss commented Jun 21, 2026

Copy link
Copy Markdown
Member

release-notes reads its lower bound (the previous tag) when a run starts, before the run tags itself, so two quick releases would produce overlapping notes. concurrency is a per-workflow key and can't live in the actions, so each release workflow must add it. Document the required block, why moving the notes step later doesn't fix it, and the cancel-in-progress trade-off.

release-notes reads its lower bound (the previous tag) when a run starts,
before the run tags itself, so two quick releases would produce overlapping
notes. concurrency is a per-workflow key and can't live in the actions, so
each release workflow must add it. Document the required block, why moving
the notes step later doesn't fix it, and the cancel-in-progress trade-off.

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: Sebastian Hoß <seb@xn--ho-hia.de>
@sebhoss sebhoss merged commit f10d6bf into main Jun 21, 2026
4 checks passed
@sebhoss sebhoss deleted the docs/release-concurrency-note branch June 21, 2026 08:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant