Skip to content

ci(release): add concurrency group so duplicate releases don't race - #424

Merged
Chris-Wolfgang merged 2 commits into
mainfrom
fix/release-concurrency-group
Jun 27, 2026
Merged

ci(release): add concurrency group so duplicate releases don't race#424
Chris-Wolfgang merged 2 commits into
mainfrom
fix/release-concurrency-group

Conversation

@Chris-Wolfgang

Copy link
Copy Markdown
Owner

Summary

release.yaml had a permissions: block but no concurrency: group — unlike pr.yaml / codeql.yaml / benchmarks.yaml. A duplicate or re-published release: published event could run two publish pipelines against NuGet and gh-pages at once.

Adds a release-scoped concurrency group with cancel-in-progress: false (never cancel an in-flight release — a half-published package family is worse than a queued one):

concurrency:
  group: release-${{ github.event.release.tag_name || github.ref }}
  cancel-in-progress: false

Surfaced by the code-review pass on ETL-FixedWidth; release.yaml is canonical, so fixing here for fleet sync.

The other workflow nit from that review — actions/checkout @v6/@v7 drift — is Dependabot-managed (the github-actions ecosystem bumps it fleet-wide) and self-heals, so it's intentionally not hand-edited here.

release.yaml had a permissions block but no concurrency: group — unlike
pr.yaml/codeql.yaml/benchmarks.yaml. A duplicate or re-published `release:
published` event could therefore run two publish pipelines against NuGet and
gh-pages simultaneously. Add a release-scoped concurrency group with
cancel-in-progress: false (never cancel an in-flight release — a half-published
package family is worse than a queued one).

Surfaced by the code-review pass on ETL-FixedWidth; release.yaml is canonical,
so fixing here for fleet sync rather than diverging one repo.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@Chris-Wolfgang
Chris-Wolfgang merged commit f8b001a into main Jun 27, 2026
6 of 7 checks passed
@Chris-Wolfgang
Chris-Wolfgang deleted the fix/release-concurrency-group branch June 27, 2026 21:29
This was referenced Jun 30, 2026
Chris-Wolfgang added a commit to Chris-Wolfgang/DbContextBuilder that referenced this pull request Jun 30, 2026
…366)

## Summary

Adds a top-level `concurrency:` group to `release.yaml` so a duplicate
or re-published `release: published` event can't run two publish
pipelines against NuGet and gh-pages at once. `cancel-in-progress:
false` — never cancel an in-flight release.

Canonical fix from Chris-Wolfgang/repo-template#424, fanned out to the
fleet. `release.yaml` is a protected file, so this needs a maintainer
admin-bypass merge.

🤖 Generated with [Claude Code](https://claude.com/claude-code)
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.

1 participant