Repository navigation
ci(extended): give each release's run a concurrency group of its own - #237
Merged
Merged
Conversation
The runs of extended.yml on main shared one concurrency group, and GitHub keeps one pending run per group, cancelling the one waiting before it. Releasing 0.9.66 and 0.9.67 minutes apart queued 0.9.66's run behind 0.9.65's, and 0.9.67's dispatch then cancelled it before it started, so 0.9.66 was never checked. The release a run is for is now part of its group, so each release's run waits for nothing and is cancelled by nothing; back to back releases are checked side by side. Each run is also named after the release it checks. Assisted-by: Claude Code:claude-opus-5-5 Signed-off-by: Simon A. F. Lund <os@safl.dk>
Coverage Report for CI Build 40876183417Warning No base build found for commit Coverage: 62.623%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsRequires a base build to compare against. How to fix this → Coverage Stats
💛 - Coveralls |
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.
extended.yml's runs on main shared one concurrency group, and GitHub keeps only one pending run per group, so a release made while the previous one's run was still going cancelled the run waiting between them. 0.9.66's run (40872729577) was cancelled that way, with no jobs, when 0.9.67 was released four minutes later; it has been dispatched again by hand (40876081452). The release a run checks is now part of its group, so every release gets its own run, and each run is named after its release.No version bump, so merging this releases nothing. Not exercised before merging: the group and the run name only take effect on main, at the next release or dispatch; actionlint passes on the change.