Skip to content

fix(release): concurrency-group deadlock between release.yml and called publish.yml#78

Merged
I4cTime merged 1 commit into
mainfrom
fix/release-concurrency
Jul 11, 2026
Merged

fix(release): concurrency-group deadlock between release.yml and called publish.yml#78
I4cTime merged 1 commit into
mainfrom
fix/release-concurrency

Conversation

@I4cTime

@I4cTime I4cTime commented Jul 11, 2026

Copy link
Copy Markdown
Owner

Summary

The v0.13.0 tag push deadlocked in 7 seconds: release.yml held concurrency group publish while calling publish.yml via workflow_call — the called workflow's own publish group 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 called publish.yml keeps publish (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.0

A follow-up PR applies the same one-file fix to develop to keep the trees identical.

Type

  • Fix

Checklist

  • Workflow YAML validates
  • No code changes — typecheck/lint/test unaffected

Breaking changes

None.

🤖 Generated with Claude Code

…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
I4cTime merged commit d1f546e into main Jul 11, 2026
9 checks passed
@I4cTime
I4cTime deleted the fix/release-concurrency branch July 11, 2026 06:47
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>
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