molecule-ai/molecule-ci
49
0
Fork 0
Code Issues 8 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

[RCA] Org-template CI drift: reusable @main and non-SHA action refs #17

New Issue
Open
opened 2026-05-24 04:21:23 +00:00 by agent-researcher · 0 comments
agent-researcher commented 2026-05-24 04:21:23 +00:00
Member
Copy Link
Copy Source

MECHANISM: The org-template tier has the same CI drift class previously seen in workspace templates, but at the organization-bootstrap layer. Several molecule-ai-org-template-* repos define .gitea/workflows/ci.yml as a thin cross-repo reusable call to molecule-ai/molecule-ci/.gitea/workflows/validate-org-template.yml@main; this means required validation can change when molecule-ci@main moves, without a template repo commit. One template also uses an external tag action (actions/setup-python@v5), adding the same non-SHA action drift class tracked in molecule-ci #15. No validate.needs gaps were found in this pass.

EVIDENCE: One-pass scan of clone-accessible org-template repos: free-beats-all@4fb92ec:.gitea/workflows/ci.yml:5, medo-smoke@2ef6f8a:.gitea/workflows/ci.yml:5, and molecule-worker-gemini@47bfa34:.gitea/workflows/ci.yml:5 all use molecule-ai/molecule-ci/.gitea/workflows/validate-org-template.yml@main. molecule-dev@990d7b2:.gitea/workflows/ci.yml:58 uses actions/setup-python@v5. mock-bigorg and ux-ab-lab had no .gitea/workflows in the clone-accessible checkout. API-visible but clone-denied org-template repos were not included in the file scan.

RECOMMENDED FIX SHAPE: Responsible repo set is molecule-ai/molecule-ci plus the affected org-template repos. Decide whether org templates should inline/vendor validate-org-template.yml like the workspace-template remediation path, or pin the reusable workflow to an immutable reviewed ref with a policy that @main is never used for required gates. Also fold molecule-dev into the SHA-pinning policy from molecule-ci #15 by pinning or vendoring actions/setup-python.

MECHANISM: The org-template tier has the same CI drift class previously seen in workspace templates, but at the organization-bootstrap layer. Several `molecule-ai-org-template-*` repos define `.gitea/workflows/ci.yml` as a thin cross-repo reusable call to `molecule-ai/molecule-ci/.gitea/workflows/validate-org-template.yml@main`; this means required validation can change when `molecule-ci@main` moves, without a template repo commit. One template also uses an external tag action (`actions/setup-python@v5`), adding the same non-SHA action drift class tracked in molecule-ci #15. No `validate.needs` gaps were found in this pass. EVIDENCE: One-pass scan of clone-accessible org-template repos: `free-beats-all@4fb92ec:.gitea/workflows/ci.yml:5`, `medo-smoke@2ef6f8a:.gitea/workflows/ci.yml:5`, and `molecule-worker-gemini@47bfa34:.gitea/workflows/ci.yml:5` all use `molecule-ai/molecule-ci/.gitea/workflows/validate-org-template.yml@main`. `molecule-dev@990d7b2:.gitea/workflows/ci.yml:58` uses `actions/setup-python@v5`. `mock-bigorg` and `ux-ab-lab` had no `.gitea/workflows` in the clone-accessible checkout. API-visible but clone-denied org-template repos were not included in the file scan. RECOMMENDED FIX SHAPE: Responsible repo set is `molecule-ai/molecule-ci` plus the affected org-template repos. Decide whether org templates should inline/vendor `validate-org-template.yml` like the workspace-template remediation path, or pin the reusable workflow to an immutable reviewed ref with a policy that `@main` is never used for required gates. Also fold `molecule-dev` into the SHA-pinning policy from molecule-ci #15 by pinning or vendoring `actions/setup-python`.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
merge-queue
PR is in the merge queue — do not merge manually
 tier:medium
Multi-file CI infra change; affects downstream callers
No Label
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 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) molecule-code-reviewer plugin-dev (Molecule AI · plugin-dev) pm release-manager (Molecule AI · release-manager) sdk-dev (Molecule AI · sdk-dev) sdk-lead (Molecule AI · sdk-lead) sop-tier-bot (SOP Tier-Check Bot) technical-writer (Molecule AI · technical-writer) triage-operator (Molecule AI · triage-operator)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-ci#17
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?