fix: remove concurrency block from reusable workflow to prevent deadlock (#829)

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) <noreply@anthropic.com>
This commit is contained in:
Frostebite
2026-05-03 17:35:15 +01:00
committed by GitHub
parent ef0555fb0d
commit d10fd10a95

View File

@@ -21,9 +21,9 @@ permissions:
checks: write checks: write
statuses: write statuses: write
concurrency: # Note: no concurrency block here — when invoked via workflow_call, the caller
group: ${{ github.workflow }}-${{ github.ref }} # (integrity-check.yml) manages concurrency. For direct dispatch/cron, runs are
cancel-in-progress: true # naturally serialized by GitHub's single-concurrency-per-ref default.
env: env:
AWS_STACK_NAME: game-ci-team-pipelines AWS_STACK_NAME: game-ci-team-pipelines