From cc4f23f7ec8ea93546a92250ca3844f539219521 Mon Sep 17 00:00:00 2001 From: Molecule AI Core-DevOps Date: Thu, 14 May 2026 01:39:24 +0000 Subject: [PATCH] fix(ci): add canvas-deploy-reminder to all-required.needs (mc#922) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit mc#922/#923 ci-drift root fix. canvas-deploy-reminder exists in ci.yml and emits `ci / canvas-deploy-reminder (pull_request)` status, but was not listed in `all-required.needs:` — causing drift detector F1 on both main and staging. Add it to the sentinel needs. Co-Authored-By: Claude Opus 4.7 --- .gitea/workflows/ci.yml | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/.gitea/workflows/ci.yml b/.gitea/workflows/ci.yml index 84bd0d84..4a0bca28 100644 --- a/.gitea/workflows/ci.yml +++ b/.gitea/workflows/ci.yml @@ -575,10 +575,12 @@ jobs: # hourly if this list diverges from status_check_contexts or from # audit-force-merge.yml's REQUIRED_CHECKS env (RFC §4 + §6). # - # Excluded from `needs:`: `canvas-deploy-reminder` — it is an - # operational reminder, not a CI prerequisite. Keep that job runnable - # on PRs with an internal no-op guard; job-level event/ref `if:` gates - # are a Gitea 1.22.6 pending-status trap. + # mc#922/#923 fix: canvas-deploy-reminder added to needs: above. + # Originally excluded because it was an operational reminder, but the + # drift detector now includes it in expected contexts, so it must be + # in the sentinel needs to avoid F1 drift. Keep it runnable on PRs + # via its own `needs: [changes, canvas-build]` — the sentinel only + # aggregates the result. # # Phase 3 (RFC #219 §1) safety: underlying build jobs carry # continue-on-error: true so their failures are masked to null (2026-05-12: re-enabled mc#774 interim) @@ -596,6 +598,7 @@ jobs: - changes - platform-build - canvas-build + - canvas-deploy-reminder - shellcheck - python-lint if: ${{ always() }} -- 2.45.2