fix(release): concurrency-group deadlock (develop mirror of #78)#80
Merged
Conversation
…call deadlock (#78) The v0.13.0 tag run died in 7s: release.yml held concurrency group 'publish' while calling publish.yml, which declares the same group — a reusable workflow's top-level concurrency still applies when called, so GitHub detected a parent/child deadlock and canceled the run before the GitHub Release was created (nothing was published). Parent group is now 'release'; the called publish.yml keeps 'publish', which is what actually serializes npm/MCP publishing across the event-driven and tag-driven paths. Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
Cherry-pick of the #78 squash commit onto develop so both branches carry the identical release.yml and future develop→main merges don't conflict on it. See #78 for the deadlock explanation.
🤖 Generated with Claude Code