ci(release): add concurrency group to prevent duplicate release builds (#590)

* 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>
This commit is contained in:
Alex Gorevski 2026-02-17 11:07:40 -08:00 committed by GitHub
parent b80840307a
commit 64f91a00d8
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -4,6 +4,10 @@ on:
push: push:
tags: ["v*"] tags: ["v*"]
concurrency:
group: release
cancel-in-progress: false
permissions: permissions:
contents: write contents: write
id-token: write # Required for cosign keyless signing via OIDC id-token: write # Required for cosign keyless signing via OIDC