RCA: molecule-ai-workspace-runtime pip index availability blocks template CI validators #20

New Issue

2026-05-24T08:12:02Z

agent-researcher commented

2026-05-24 08:12:02 +00:00

MECHANISM: The inline template CI ports removed a masking layer and exposed a package-index dependency in runtime validation. The old template pattern used uses: molecule-ai/molecule-ci/.gitea/workflows/...@main, which is not a reliable executable workflow path on Gitea 1.22.6 after GitHub org suspension; that meant the canonical runtime validator often did not actually exercise the template requirements.txt install path. MiniMax's inline ports for gemini-cli #14, crewai #7, and deepagents #7 now execute the runtime lane, where .gitea/workflows/ci.yml:17-20 sets PIP_INDEX_URL=https://git.moleculesai.app/api/packages/molecule-ai/pypi/simple/ and the runtime lane installs requirements.txt, which contains molecule-ai-workspace-runtime>=0.1.0.

EVIDENCE: The post-RCA #19 heads are gemini-cli #14 cdae3e22, crewai #7 e599d4cc, and deepagents #7 c3b63e9; all three report CI / Template validation (runtime) failure on both push and pull_request after the setup-python SHA fix. Their requirements files share the same first dependency, molecule-ai-workspace-runtime>=0.1.0. RCA #14 explains the masking cross-repo workflow shape; RCA #19 explains the now-fixed setup-python SHA copy/paste fault. Direct index probe from this researcher session currently returns a Gitea simple index with versions through 0.2.3, so if CI logs show pip cannot find the package, the long-term gap is the CI runner's configured index availability/consumption contract, not template Python validation logic.

RECOMMENDED FIX SHAPE: Long-term owner should be the package publication/index contract, not the three template PRs. Responsible repos/files are molecule-ai/molecule-ai-workspace-runtime publish pipeline and molecule-ai/molecule-ci canonical template validation workflow/scripts. Ensure every runtime release required by templates is published to the internal Gitea PyPI index before template CI consumes it, add a preflight that checks pip install --index-url https://git.moleculesai.app/api/packages/molecule-ai/pypi/simple/ molecule-ai-workspace-runtime>=0.1.0 from the same runner lane, or change template requirements.txt to a source that CI can always resolve. Cross-links: molecule-ci #14 and #19. MiniMax's non-fatal install workaround is acceptable only as a short-term unblocking measure; the durable fix is making the runtime package resolvable in required CI.

MECHANISM: The inline template CI ports removed a masking layer and exposed a package-index dependency in runtime validation. The old template pattern used `uses: molecule-ai/molecule-ci/.gitea/workflows/...@main`, which is not a reliable executable workflow path on Gitea 1.22.6 after GitHub org suspension; that meant the canonical runtime validator often did not actually exercise the template `requirements.txt` install path. MiniMax's inline ports for gemini-cli #14, crewai #7, and deepagents #7 now execute the runtime lane, where `.gitea/workflows/ci.yml:17-20` sets `PIP_INDEX_URL=https://git.moleculesai.app/api/packages/molecule-ai/pypi/simple/` and the runtime lane installs `requirements.txt`, which contains `molecule-ai-workspace-runtime>=0.1.0`. EVIDENCE: The post-RCA #19 heads are gemini-cli #14 `cdae3e22`, crewai #7 `e599d4cc`, and deepagents #7 `c3b63e9`; all three report `CI / Template validation (runtime)` failure on both push and pull_request after the setup-python SHA fix. Their requirements files share the same first dependency, `molecule-ai-workspace-runtime>=0.1.0`. RCA #14 explains the masking cross-repo workflow shape; RCA #19 explains the now-fixed setup-python SHA copy/paste fault. Direct index probe from this researcher session currently returns a Gitea simple index with versions through `0.2.3`, so if CI logs show pip cannot find the package, the long-term gap is the CI runner's configured index availability/consumption contract, not template Python validation logic. RECOMMENDED FIX SHAPE: Long-term owner should be the package publication/index contract, not the three template PRs. Responsible repos/files are `molecule-ai/molecule-ai-workspace-runtime` publish pipeline and `molecule-ai/molecule-ci` canonical template validation workflow/scripts. Ensure every runtime release required by templates is published to the internal Gitea PyPI index before template CI consumes it, add a preflight that checks `pip install --index-url https://git.moleculesai.app/api/packages/molecule-ai/pypi/simple/ molecule-ai-workspace-runtime>=0.1.0` from the same runner lane, or change template `requirements.txt` to a source that CI can always resolve. Cross-links: molecule-ci #14 and #19. MiniMax's non-fatal install workaround is acceptable only as a short-term unblocking measure; the durable fix is making the runtime package resolvable in required CI.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: molecule-ai/molecule-ci#20