ci: scope release concurrency group per branch#15519
Merged
Merged
Conversation
This was referenced May 21, 2026
gr2m
added a commit
that referenced
this pull request
May 21, 2026
## Summary - Backport of #15519 to `release-v6.0`. - Change `concurrency.group` in `.github/workflows/release.yml` from a single global `'release'` to `'release-${{ github.ref }}'` so each release branch (`main`, `release-v6.0`, `release-v5.0`) gets its own concurrency slot. ## Why All three Release runs currently share one concurrency group. With `cancel-in-progress: false`, GitHub queues at most one pending run per group, so when pushes land on multiple branches within seconds (as today across #15509, #15513, #15517), the middle pending run gets bumped from the queue and canceled — e.g. run [26246209250](https://github.com/vercel/ai/actions/runs/26246209250). Scoping the group per branch lets each branch's Release workflow run independently while still serializing within a single branch. ## Test plan - [ ] Land on `main` (#15519), `release-v6.0`, and `release-v5.0` - [ ] Verify overlapping pushes across branches no longer cancel each other
gr2m
added a commit
that referenced
this pull request
May 21, 2026
## Summary - Backport of #15519 to `release-v5.0`. - Change `concurrency.group` in `.github/workflows/release.yml` from a single global `'release'` to `'release-${{ github.ref }}'` so each release branch (`main`, `release-v6.0`, `release-v5.0`) gets its own concurrency slot. ## Why All three Release runs currently share one concurrency group. With `cancel-in-progress: false`, GitHub queues at most one pending run per group, so when pushes land on multiple branches within seconds (as today across #15509, #15513, #15517), the middle pending run gets bumped from the queue and canceled — e.g. run [26246209250](https://github.com/vercel/ai/actions/runs/26246209250). Scoping the group per branch lets each branch's Release workflow run independently while still serializing within a single branch. ## Test plan - [ ] Land on `main` (#15519), `release-v6.0` (#15520), and `release-v5.0` - [ ] Verify overlapping pushes across branches no longer cancel each other
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.
Summary
concurrency.groupin.github/workflows/release.ymlfrom a single global'release'to'release-${{ github.ref }}'so each release branch (main,release-v6.0,release-v5.0) gets its own concurrency slot.Why
Today all three Release runs share one concurrency group. With
cancel-in-progress: false, GitHub queues at most one pending run per group — so when three pushes arrive in quick succession (as happened today on #15509, #15513, #15517), the middle pending run gets bumped out of the queue and canceled. Run 26246209250 was canceled this way.Scoping the group per branch lets each branch's Release workflow run independently while still serializing runs within a single branch.
Test plan
release-v6.0andrelease-v5.0branches