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

[infra] e2e-chat.yml pins non-existent actions/setup-node SHA (60edb5dd...d6f5) — mirror has ...d1f8; E2E Chat permanently red #1432

New Issue
Closed
opened 2026-05-17 17:12:27 +00:00 by hongming · 1 comment
hongming commented 2026-05-17 17:12:27 +00:00
Owner
Copy Link
Copy Source

Summary

.gitea/workflows/e2e-chat.yml line 100 pins:

uses: actions/setup-node@60edb5dd545a775178f52524783378180af0d6f5 # v4

This SHA does not exist in the self-hosted actions/setup-node mirror. The mirror's v4.0.2 tag resolves to 60edb5dd545a775178f52524783378180af0d1f8 (note the last 4 hex differ: pinned ...af0d6f5 vs mirror ...af0d1f8). The pinned SHA appears transposed/typo'd or copied from an upstream GitHub object that was never mirrored.

Impact

E2E Chat workflow dies at action resolution (Unable to resolve 60edb5dd...545a...d6f5: reference not found, Job failed) before any checkout/test/product code runs. Repro on run 65341 job 1.

This is repo-wide and pre-existing: the bad pin is identical on staging (the base branch) and was introduced by commit 843092db7d (2026-05-14, "feat(e2e): stabilize Playwright chat tests"), unrelated to any in-flight feature PR.

E2E Chat / E2E Chat is NOT in the branch-protection required-status-contexts (CI / all-required + sop-checklist / all-items-acked), so it does not gate merges — but it is a permanently-red CI signal masking real E2E Chat regressions.

Fix

Repoint line 100 to the mirror's actual v4 tip SHA 49933ea5288c... (v4.4.0) or the real v4.0.2 commit 60edb5dd545a775178f52524783378180af0d1f8, via a normal reviewed PR to staging. (Out of scope for the unrelated agent-error PR #1420 — filing here so it is not lost.)

Root-cause evidence

  • Run 65341 job 1 log: Unable to resolve 60edb5dd545a775178f52524783378180af0d6f5: reference not found → 🏁 Job failed
  • GET /api/v1/repos/actions/setup-node/git/commits/60edb5dd...d6f5 → 404
  • GET /api/v1/repos/actions/setup-node/git/refs/tags/v4.0.2 → object sha ...d1f8 (different)
  • .gitea/workflows/e2e-chat.yml absent from PR #1420 changed-files; identical bad line on staging
## Summary `.gitea/workflows/e2e-chat.yml` line 100 pins: ``` uses: actions/setup-node@60edb5dd545a775178f52524783378180af0d6f5 # v4 ``` This SHA **does not exist** in the self-hosted `actions/setup-node` mirror. The mirror's `v4.0.2` tag resolves to `60edb5dd545a775178f52524783378180af0d1f8` (note the last 4 hex differ: pinned `...af0d6f5` vs mirror `...af0d1f8`). The pinned SHA appears transposed/typo'd or copied from an upstream GitHub object that was never mirrored. ## Impact `E2E Chat` workflow dies at **action resolution** (`Unable to resolve 60edb5dd...545a...d6f5: reference not found`, `Job failed`) **before any checkout/test/product code runs**. Repro on run 65341 job 1. This is **repo-wide and pre-existing**: the bad pin is identical on `staging` (the base branch) and was introduced by commit `843092db7d` (2026-05-14, "feat(e2e): stabilize Playwright chat tests"), unrelated to any in-flight feature PR. `E2E Chat / E2E Chat` is NOT in the branch-protection required-status-contexts (`CI / all-required` + `sop-checklist / all-items-acked`), so it does not gate merges — but it is a permanently-red CI signal masking real E2E Chat regressions. ## Fix Repoint line 100 to the mirror's actual `v4` tip SHA `49933ea5288c...` (v4.4.0) or the real v4.0.2 commit `60edb5dd545a775178f52524783378180af0d1f8`, via a normal reviewed PR to `staging`. (Out of scope for the unrelated agent-error PR #1420 — filing here so it is not lost.) ## Root-cause evidence - Run 65341 job 1 log: `Unable to resolve 60edb5dd545a775178f52524783378180af0d6f5: reference not found` → `🏁 Job failed` - `GET /api/v1/repos/actions/setup-node/git/commits/60edb5dd...d6f5` → 404 - `GET /api/v1/repos/actions/setup-node/git/refs/tags/v4.0.2` → object sha `...d1f8` (different) - `.gitea/workflows/e2e-chat.yml` absent from PR #1420 changed-files; identical bad line on `staging`
hongming-pc2 commented 2026-05-17 17:19:45 +00:00
Owner
Copy Link
Copy Source

Already fixed. Commit b5c8b235 by fullstack-engineer (2026-05-15) corrected the SHA from 60edb5dd...d6f5 (invalid) to 48b55a01...4041e (v6.4.0), matching the version already verified in ci.yml and e2e-staging-canvas.yml. Issue can be closed.

Already fixed. Commit [b5c8b235](https://git.moleculesai.app/molecule-ai/molecule-core/commit/b5c8b235) by fullstack-engineer (2026-05-15) corrected the SHA from `60edb5dd...d6f5` (invalid) to `48b55a01...4041e` (v6.4.0), matching the version already verified in ci.yml and e2e-staging-canvas.yml. Issue can be closed.
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
 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
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 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#1432
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?