From 155e20af392cdb85322095eb96b64d164c8fb3f8 Mon Sep 17 00:00:00 2001 From: Sam Catlow Date: Wed, 2 Sep 2026 00:14:57 +1000 Subject: [PATCH] ci(deploy): key concurrency group on commit SHA, not ref git push --follow-tags pushes main plus both archied/v* and archie/v* tags in one operation, all pointing at the same commit. on.push matches branches and tags, so every release push fired three identical deploy runs -- observed just now: archied/v1.19.7, archie/v1.19.7, and main all running in parallel from the same commit. The ref-keyed concurrency group added earlier couldn't see these as the same work since github.ref differs per trigger. Key on github.sha instead so all three collapse into one. --- .github/workflows/deploy.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml index 71ec442e0..06ce1d0b6 100644 --- a/.github/workflows/deploy.yml +++ b/.github/workflows/deploy.yml @@ -14,8 +14,14 @@ on: # three deploys racing in parallel for the same runner capacity. Only the # last one's images matter (both jobs push :latest), so cancel a # superseded run rather than let it fight for resources it can't use. +# +# Keyed on the commit, not github.ref: `git push --follow-tags` pushes +# main plus both archied/v* and archie/v* tags in one go, and all three +# refs point at the same commit -- on.push matches branches and tags +# both, so a single release push otherwise fires three redundant builds +# of identical content that a ref-keyed group can't see as the same work. concurrency: - group: deploy-${{ github.ref }} + group: deploy-${{ github.sha }} cancel-in-progress: true permissions: