fix: give the pipeline its own concurrency group to avoid a publish deadlock - #32
Merged
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the GitHub Actions release pipeline workflow to avoid a concurrency deadlock when it calls the nested publish.yml reusable workflow by giving the pipeline its own distinct concurrency group.
Changes:
- Change
.github/workflows/release-pipeline.ymlconcurrency group fromnpm-publishtonpm-releaseto prevent parent/child workflow concurrency group collisions.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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.
release-pipeline.ymland thepublish.ymlit calls both used thenpm-publishconcurrency group. A nested workflow sharing its caller's group deadlocks, so every publish run got canceled.Renames the pipeline's group to
npm-release.publish.ymlkeepsnpm-publish, so the actual npm-publish step still serializes across both the pipeline and standalone runs, with no parent/child clash.