Repository navigation
Add concurrency groups to CI and the release workflows - #35
Merged
Merged
Conversation
CI cancels the run in flight when a newer push lands on the same ref. release-github and release-mcp-registry queue per tag and never cancel, so a second dispatch for the same tag waits instead of racing the first. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
Added concurrency groups to CI and release workflows to control parallel runs and cancellations. The CI workflow cancels in-progress runs on the same ref to avoid queuing redundant matrix jobs. The release workflows group by release tag and do not cancel in-progress runs to prevent partial or conflicting releases. This ensures orderly and efficient workflow execution.
Automated review by siGit Code Review · commit 3684d1e · see the review dashboard
paydii
approved these changes
Oct 11, 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.
What
ci.yml: group by ref and cancel the run in flight when a newer push lands, so a burst of pushes doesn't queue a full ubuntu + macOS matrix for each one.release-github.ymlandrelease-mcp-registry.yml: group by release tag and never cancel. A second dispatch for the same tag waits for the first instead of racing it. Cancelling a half-built release or a mid-publishmcp-publishercould leave things half done.release-crates.yml(#32) already has its own group, also without cancelling.Checked
Only workflow files changed, so there is nothing to build locally. The CI group takes effect on the first push after this merges.