Serialize release workflow to prevent major-tag race conditions#1266
Merged
v1v merged 2 commits intoJun 23, 2026
Conversation
Copilot
AI
changed the title
[WIP] Fix release workflow to serialize major tag updates
Serialize release workflow to prevent major-tag race conditions
Jun 15, 2026
v1v
approved these changes
Jun 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The release workflow force-updates floating major tags (
v0,v1) without serialization. Concurrent releases can race on the same major tag, potentially leaving it at an unintended commit.Changes
Added workflow-level
concurrencyblock to.github/workflows/release.yml:This serializes all release runs. The global group prevents concurrent execution;
cancel-in-progress: falseensures queued releases complete sequentially rather than being cancelled.