From f2a7fdacfe4e4fa4443951d855388e593f06e356 Mon Sep 17 00:00:00 2001 From: Ethan <39577870+ethanndickson@users.noreply.github.com> Date: Mon, 30 Mar 2026 20:46:21 +1100 Subject: [PATCH] ci: don't cancel in-progress linear release runs on main (#23766) The Linear Release workflow had `cancel-in-progress: true` unconditionally, so a new push to `main` would cancel an already-running sync. This meant successive PR merges would show you a bunch of red Xs on CI, even though nothing was wrong. image Other workflows like CI guard against this with `cancel-in-progress: ${{ github.ref != 'refs/heads/main' }}`. This PR does the same thing to the linear release workflow. The job will be queued instead. image Letting the job finish is not particularly wasteful or anything since the sync takes 30~ seconds in CI time. --- .github/workflows/linear-release.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/workflows/linear-release.yaml b/.github/workflows/linear-release.yaml index 5c40ba32d1..44094c7c71 100644 --- a/.github/workflows/linear-release.yaml +++ b/.github/workflows/linear-release.yaml @@ -13,7 +13,8 @@ permissions: concurrency: group: ${{ github.workflow }}-${{ github.ref }} - cancel-in-progress: true + # Queue rather than cancel so back-to-back pushes to main don't cancel the first sync. + cancel-in-progress: false jobs: sync-main: