From d10fd10a95ab53581b9c781da2891b3ae8908a89 Mon Sep 17 00:00:00 2001 From: Frostebite Date: Sun, 3 May 2026 17:35:15 +0100 Subject: [PATCH] fix: remove concurrency block from reusable workflow to prevent deadlock (#829) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit When integrity-check.yml calls validate-orchestrator-integration.yml via workflow_call, both workflows resolve github.workflow to the same name ("Integrity"), creating identical concurrency groups. GitHub detects this as a deadlock and cancels the run. Fix: remove concurrency from the reusable workflow entirely — the caller already manages concurrency for the group. Co-authored-by: Claude Opus 4.6 (1M context) --- .github/workflows/validate-orchestrator-integration.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/workflows/validate-orchestrator-integration.yml b/.github/workflows/validate-orchestrator-integration.yml index b51a248d..746ae59f 100644 --- a/.github/workflows/validate-orchestrator-integration.yml +++ b/.github/workflows/validate-orchestrator-integration.yml @@ -21,9 +21,9 @@ permissions: checks: write statuses: write -concurrency: - group: ${{ github.workflow }}-${{ github.ref }} - cancel-in-progress: true +# Note: no concurrency block here — when invoked via workflow_call, the caller +# (integrity-check.yml) manages concurrency. For direct dispatch/cron, runs are +# naturally serialized by GitHub's single-concurrency-per-ref default. env: AWS_STACK_NAME: game-ci-team-pipelines