ci(staging): remove canvas-deploy-reminder from all-required.needs (deadlock fix) #944

Closed
core-devops wants to merge 1 commits from fix/staging-canvas-reminder-deadlock into staging

1 Commits

Author SHA1 Message Date
8f4c252c94 ci(staging): remove canvas-deploy-reminder from all-required.needs (deadlock fix)
Some checks failed
Block internal-flavored paths / Block forbidden paths (pull_request) Successful in 18s
CI / Detect changes (pull_request) Successful in 36s
sop-checklist / na-declarations (pull_request) awaiting /sop-n/a declaration for: qa-review, security-review
CI / Shellcheck (E2E scripts) (pull_request) Successful in 19s
sop-checklist / all-items-acked (pull_request) ok
CI / Python Lint & Test (pull_request) Failing after 7m29s
CI / all-required (pull_request) Blocked by required conditions
CI / Platform (Go) (pull_request) Failing after 8m25s
CI / Canvas (Next.js) (pull_request) Failing after 13m31s
CI / Canvas Deploy Reminder (pull_request) Has been skipped
The mc#923 fix (PR #927) introduced a permanent CI hang on every
CI-only PR: canvas-deploy-reminder is in all-required.needs, but it
itself needs canvas-build which is skipped when canvas=false. The
all-required sentinel waits forever for a job that never runs on
CI-only PRs.

Fix: exclude canvas-deploy-reminder from all-required.needs on staging
(the same fix as PR #938 targeting main).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-14 03:25:46 +00:00