fix: prioritize rollback over queued deploys

2026-06-23 18:44:42 +02:00
parent 1214cf9a4d
commit 68b428e411
2 changed files with 7 additions and 2 deletions
@@ -18,9 +18,12 @@ run-name: 🔙 Rollback by @${{ gitea.actor }}
 # migrations). If the tag predates a destructive migration, manual
 # DB intervention is needed — that's an edge case surfaced to DevOps.
 # ───────────────────────────────────────────────────────
+# Rollback wins over queued/in-progress deploys.
+# It shares deploy-production with deploy.yaml so rollback and deploy never run together,
+# but cancel-in-progress=true prevents a queued auto-deploy from running after rollback.
 concurrency:
  group: deploy-production
-  cancel-in-progress: false
+  cancel-in-progress: true

 on:
  workflow_dispatch: