fix: treat pending Gitea CI as acceptable on synced main

Normal Portal releases should not block when commit status stays pending after the candidate is already pushed to origin/main. Co-authored-by: Cursor <cursoragent@cursor.com>
2026-07-27 22:36:40 +08:00
parent 82b74d71ad
commit a95681ea3a
3 changed files with 17 additions and 6 deletions
@@ -60,8 +60,14 @@ export function isReleaseCiAcceptable(ciStatus, { headSha, remoteSha } = {}) {
  const normalized = String(ciStatus ?? 'missing').trim().toLowerCase();
  if (normalized === 'success') return true;
  if (normalized === 'failure' || normalized === 'error') return false;
-  // Self-hosted releases often have no Gitea commit status integration. Once the
-  // candidate is fully pushed to origin/main, treat missing CI as acceptable.
-  if (normalized === 'missing' && remoteSha && headSha === remoteSha) return true;
+  // Self-hosted releases often have no meaningful Gitea commit status. Once the
+  // candidate is fully pushed to origin/main, treat missing/pending CI as acceptable.
+  if (
+    (normalized === 'missing' || normalized === 'pending')
+    && remoteSha
+    && headSha === remoteSha
+  ) {
+    return true;
+  }
  return false;
 }