Skip to content

ci(extended): give each release's run a concurrency group of its own - #237

Merged
safl merged 1 commit into
mainfrom
extended-per-release
Oct 29, 2026
Merged

safl merged 1 commit into
mainfrom
extended-per-release

Conversation

@safl

@safl safl commented Oct 29, 2026

Copy link
Copy Markdown
Collaborator

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.

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>
@coveralls

Copy link
Copy Markdown

Coverage Report for CI Build 40876183417

Warning

No base build found for commit b064116 on main.
Coverage changes can't be calculated without a base build.
If a base build is processing, this comment will update automatically when it completes.

Coverage: 62.623%

Details

  • Patch coverage: No coverable lines changed in this PR.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

Requires a base build to compare against. How to fix this →


Coverage Stats

Coverage Status
Relevant Lines: 3149
Covered Lines: 2026
Line Coverage: 64.34%
Relevant Branches: 1204
Covered Branches: 700
Branch Coverage: 58.14%
Branches in Coverage %: Yes
Coverage Strength: 0.64 hits per line

💛 - Coveralls

@safl
safl merged commit 93cd9d2 into main Oct 29, 2026
22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants