ci: don't cancel main/release CI runs on concurrency conflicts - #1083
Merged
Merged
Conversation
cancel-in-progress applied to pushes on main too, so a rapid follow-up merge could cancel the CI run for a release-please release commit. Since the Release workflow only fires on a "success" conclusion, the cancelled run silently skipped publishing the release (missed v2.50.0). Now only PR runs get cancelled on new pushes.
Coverage Report for CI Build 28809474833Coverage remained the same at 83.168%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
grdsdev
changed the title
spydon
approved these changes
Jul 7, 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
3 participants
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
ci-${{ github.ref }}withcancel-in-progress: truescoped to the branch ref meant every push tomainshared one group — a follow-up push landing while a previous main CI run was still in flight would cancel it.release.ymlonly invokes release-please when the triggering CIworkflow_runconcludes withsuccess, so a cancelled run silently skips publishing any pending release.pull_requestevents (fast feedback on new commits to an open PR); pushes tomain/release/*always run to completion so the release gate isn't broken by unrelated concurrent merges.Recovery
Manually dispatched
release.ymlviaworkflow_dispatchto unblock the pending release — v2.50.0 is now tagged and published on commit 102a146.Test plan
gh api .../check-runsandgh run listhistory (cancelled CI run → skipped Release workflow_run)pull_request)mainthat both CI runs complete instead of the first being cancelled