From 12f261102473edca76c2d3c2a99cccd589b5206f Mon Sep 17 00:00:00 2001 From: rcourtman Date: Fri, 17 Jul 2026 16:47:00 +0100 Subject: [PATCH] fix(ci): stop cancelling in-progress Build and Test runs cancel-in-progress meant a busy main never completed a verdict: four consecutive runs were cancelled by follow-up pushes this afternoon, so the workflow produced neither green nor red for hours. Adopt the Core E2E concurrency policy instead and let the in-progress run finish while queued runs collapse to the newest pending one. --- .github/workflows/build-and-test.yml | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/.github/workflows/build-and-test.yml b/.github/workflows/build-and-test.yml index fa04f8393..0d292576f 100644 --- a/.github/workflows/build-and-test.yml +++ b/.github/workflows/build-and-test.yml @@ -14,9 +14,14 @@ on: permissions: contents: read +# Let the in-progress run finish (pushes land here every few minutes on a +# busy day, and cancelling would mean main never completes a verdict — four +# consecutive runs were cancelled on 2026-07-17 alone); queued runs collapse +# to the newest pending one, so intermediate pushes skip. Mirrors the Core +# E2E workflow's concurrency policy. concurrency: group: ${{ github.workflow }}-${{ github.ref }} - cancel-in-progress: true + cancel-in-progress: false jobs: secret-scan: