fix(release): concurrency-group deadlock between release.yml and called publish.yml#78
Merged
Merged
Conversation
…call deadlock 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>
I4cTime
added a commit
that referenced
this pull request
Jul 11, 2026
…call deadlock (#78) (#80) 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>
4 tasks
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.
Summary
The
v0.13.0tag push deadlocked in 7 seconds:release.ymlheld concurrency grouppublishwhile callingpublish.ymlviaworkflow_call— the called workflow's ownpublishgroup still applies, so GitHub canceled the run as a parent/child deadlock. It died before the GitHub Release step, so nothing was published and the retry is clean.Fix: the parent uses group
release; the calledpublish.ymlkeepspublish(that group is what actually serializes publishing across the event-driven and tag-driven paths).After merging: move the tag to the new main head and re-push to rerun the release:
git push origin :refs/tags/v0.13.0 git tag -f v0.13.0 origin/main && git push origin v0.13.0A follow-up PR applies the same one-file fix to develop to keep the trees identical.
Type
Checklist
Breaking changes
None.
🤖 Generated with Claude Code