fix(ci): revert cancel-in-progress to true — ubuntu-runner dispatch stalled

With cancel-in-progress: false, pending CI runs accumulate in the
ci-staging concurrency group. New pushes create queued runs, but
GitHub dispatches multiple runs for the same SHA instead of replacing
the pending one. All runs get stuck/cancelled before completing.

Reverting to cancel-in-progress: true restores CI operation — runs
that are superseded are cancelled, freeing the concurrency slot for
the new run to proceed.

Runner availability (ubuntu-latest dispatch stall) is a separate
infra issue tracked independently.
This commit is contained in:
molecule-ai[bot] 2026-04-21 03:42:23 +00:00 committed by GitHub
parent 1f35128ebb
commit 23be5083e4

View File

@ -6,12 +6,12 @@ on:
pull_request:
branches: [main, staging]
# Queue new CI runs when a commit arrives on the same ref.
# New runs queue instead of cancelling each other — prevents
# the single self-hosted macOS arm64 runner from being monopolised.
# Cancel in-progress CI runs when a new commit arrives on the same ref.
# This prevents multiple stale runs from queuing behind each other and
# monopolising the self-hosted macOS arm64 runner.
concurrency:
group: ci-${{ github.ref }}
cancel-in-progress: false
cancel-in-progress: true
jobs:
# Detect which paths changed so downstream jobs can skip when only