* ci(release): add concurrency group to prevent duplicate release builds When two tags are pushed in quick succession, the release workflow could run concurrently, producing corrupted or incomplete GitHub releases. Add a concurrency group scoped to the tag ref so that release runs for the same tag are serialized. cancel-in-progress is set to false to ensure a running release completes rather than being aborted. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * ci(release): serialize all release runs globally Use a constant workflow concurrency group so release publish jobs run one-at-a-time across tags, avoiding cross-tag race conditions. --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Will Sarg <12886992+willsarg@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| auto-response.yml | ||
| ci.yml | ||
| codeql.yml | ||
| docker.yml | ||
| label-policy-sanity.yml | ||
| labeler.yml | ||
| pr-hygiene.yml | ||
| pr-intake-sanity.yml | ||
| release.yml | ||
| rust-reusable.yml | ||
| security.yml | ||
| stale.yml | ||
| update-notice.yml | ||
| workflow-sanity.yml | ||