From 878ea77e4bb891f8de026edc5a4444436e054add Mon Sep 17 00:00:00 2001 From: Yuriy Andamasov Date: Sun, 10 May 2026 23:52:06 +0300 Subject: ci: scope update-version-tags concurrency group by SHA MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Copilot review on PR #1953 surfaced an edge case the HEAD guard alone doesn't fully cover: with cancel-in-progress: true and a per-branch concurrency group, a stale "Re-run jobs" replay can cancel the in-progress run for the current branch HEAD. The stale re-run then hits the HEAD guard and exits 0, leaving the tag un-advanced until the next push. Including github.sha in the concurrency group means different commits land in different groups and never cancel each other. Same-SHA re-runs still deduplicate (they share the group), and the HEAD guard handles the case where a stale re-run beats the current-HEAD run to start. 🤖 Generated by [robots](https://vyos.io) --- .github/workflows/update-version-tags.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to '.github') diff --git a/.github/workflows/update-version-tags.yml b/.github/workflows/update-version-tags.yml index e93f63c8..04ccd1e4 100644 --- a/.github/workflows/update-version-tags.yml +++ b/.github/workflows/update-version-tags.yml @@ -14,7 +14,10 @@ permissions: contents: write concurrency: - group: version-tag-${{ github.ref_name }} + # Include github.sha so a stale "Re-run jobs" replay (which carries the + # original SHA) cannot cancel an in-progress run for the current branch + # HEAD. Same-SHA re-runs still deduplicate. + group: version-tag-${{ github.ref_name }}-${{ github.sha }} cancel-in-progress: true jobs: -- cgit v1.2.3