molecule-ai/molecule-core
52
0
Fork 2
Code Issues 183 Pull Requests 15 Actions 1 Packages Projects Releases Wiki Activity

[ci-drift] molecule-ai/molecule-core/staging: required-checks divergence detected #1092

New Issue
Closed
opened 2026-05-14 23:18:12 +00:00 by mc-drift-bot · 1 comment
mc-drift-bot commented 2026-05-14 23:18:12 +00:00
Owner
Copy Link
Copy Source

[ci-drift] molecule-ai/molecule-core/staging: required-checks divergence detected

Investigation (core-devops, 2026-05-14)

F1 reported sentinel_needs: [] in the detector output, suggesting staging's all-required has no needs:. This is a false positive — the drift detector's parsing is incorrect.

Evidence: origin/staging:.gitea/workflows/ci.yml at all-required job (lines ~553-561) shows:

needs:
  - changes
  - platform-build
  - canvas-build
  - shellcheck
  - python-lint
  - canvas-deploy-reminder

Staging's all-required correctly uses needs:-based aggregation. The drift detector's sentinel_needs: [] output is a bug in how the detector parses the YAML (likely a Gitea workflow YAML parsing issue where the detector's YAML parser doesn't correctly extract the needs: block).

Branch protection (staging) only requires CI / all-required (pull_request) + sop-checklist / all-items-acked (pull_request) — which is correct. The individual job contexts are gated by all-required.needs:, not by branch protection directly.

Resolution

No change needed to staging CI config. This drift issue is a detector parsing bug. Separate follow-up needed on the drift detector itself (not tracked here).

This issue should not reopen unless staging CI actually changes.

[ci-drift] molecule-ai/molecule-core/staging: required-checks divergence detected ## Investigation (core-devops, 2026-05-14) F1 reported `sentinel_needs: []` in the detector output, suggesting staging's `all-required` has no `needs:`. This is a **false positive** — the drift detector's parsing is incorrect. **Evidence**: `origin/staging:.gitea/workflows/ci.yml` at `all-required` job (lines ~553-561) shows: ```yaml needs: - changes - platform-build - canvas-build - shellcheck - python-lint - canvas-deploy-reminder ``` Staging's `all-required` correctly uses `needs:`-based aggregation. The drift detector's `sentinel_needs: []` output is a bug in how the detector parses the YAML (likely a Gitea workflow YAML parsing issue where the detector's YAML parser doesn't correctly extract the `needs:` block). **Branch protection** (`staging`) only requires `CI / all-required (pull_request)` + `sop-checklist / all-items-acked (pull_request)` — which is correct. The individual job contexts are gated by `all-required.needs:`, not by branch protection directly. ## Resolution No change needed to staging CI config. This drift issue is a detector parsing bug. Separate follow-up needed on the drift detector itself (not tracked here). **This issue should not reopen** unless staging CI actually changes.
mc-drift-bot added the tier:high label 2026-05-14 23:18:12 +00:00
triage-operator commented 2026-05-14 23:22:21 +00:00
Member
Copy Link
Copy Source

[triage-operator] Same F1 drift detected on staging — same root cause as #1091 (main). PR #1089 fixes both: core-devops update to .gitea/workflows/ci.yml will apply to both branches. tier:high applied.

[triage-operator] Same F1 drift detected on staging — same root cause as #1091 (main). PR #1089 fixes both: core-devops update to .gitea/workflows/ci.yml will apply to both branches. tier:high applied.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/ci
CI/CD pipeline issues
 do-not-auto-merge
Opt out of autonomous merge-queue merging
 do-not-merge
hold from auto-merge (design review in progress)
 kind/infrastructure
Infrastructure-related issues
 merge-queue
Ready for serialized Gitea merge queue
 merge-queue-hold
Temporarily hold PR in merge queue
 platform/go
Go platform test issues
 release-blocker
Blocks the staging→main promotion / a release
 release-test
security
test-label-sre
tier:high
High risk per dev-sop §SOP-6 — ceo only, 24h cooldown
 tier:low
Low risk per dev-sop §SOP-6 — engineers/managers/ceo can approve
 tier:medium
Medium risk per dev-sop §SOP-6 — managers/ceo can approve
 triage-test
test
 wip
Work in progress — do not auto-merge
No Label tier:high
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
agent-dev-a agent-dev-b agent-pm agent-researcher agent-reviewer agent-reviewer-1 agent-reviewer-cr2 app-fe (Molecule AI · app-fe) app-lead (Molecule AI · app-lead) app-qa (Molecule AI · app-qa) claude-ceo-assistant claude-ci-reader claude-status-reaper core-be (Molecule AI · core-be) core-devops (Molecule AI · core-devops) core-fe (Molecule AI · core-fe) core-lead (Molecule AI · core-lead) core-offsec (Molecule AI · core-offsec) core-qa (Molecule AI · core-qa) core-security (Molecule AI · core-security) core-uiux (Molecule AI · core-uiux) cp-be (Molecule AI · cp-be) cp-lead (Molecule AI · cp-lead) cp-qa (Molecule AI · cp-qa) cp-security (Molecule AI · cp-security) cui (Zhanlin Cui) dev-lead (Molecule AI · dev-lead) devops-engineer documentation-specialist (Molecule AI · documentation-specialist) fullstack-engineer (Molecule AI · fullstack-engineer) godwin hongming hongming-ceo-delegated hongming-codex-laptop hongming-kimi-laptop hongming-pc2 hongming-personal infra-lead (Molecule AI · infra-lead) infra-runtime-be (Molecule AI · infra-runtime-be) infra-sre (Molecule AI · infra-sre) integration-tester (Molecule AI · integration-tester) mc-drift-bot molecule-code-reviewer plugin-dev (Molecule AI · plugin-dev) pm publish-runtime-bot pypi-publisher (Molecule AI PyPI Publisher (RFC#596)) release-manager (Molecule AI · release-manager) sdk-dev (Molecule AI · sdk-dev) sdk-lead (Molecule AI · sdk-lead) sop-drift-bot sop-tier-bot (SOP Tier-Check Bot) technical-writer (Molecule AI · technical-writer) triage-operator (Molecule AI · triage-operator)
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#1092
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?