fix(ci): cherry-pick PR#23 — drop github-app-auth plugin checkout (unblocks workspace-server publish) #28
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "chore/cherry-pick-pr23-into-main"
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?
Cherry-pick of staging commit
1d8c101c(PR#23 main payload) onto core/main. Unblockspublish-workspace-server-image.ymlon every push to core/main.Why
Prod-latest audit (this dispatch) found:
molecule-ai/platformrepo doesn't exist (workspace-server platform image never published)molecule-ai/platform-tenant:latestis yesterday'sstaging-120b848(2026-05-06 22:40)Root cause:
publish-workspace-server-image.ymlon core/main HEAD6fac24e3defails atRun Main Checkout sibling plugin repobecause it tries to clonemolecule-ai/molecule-ai-plugin-github-app-authwhich was removed/unreachable post-2026-05-06 suspension.The fix landed on staging in PR#23 (commit
1d8c101c). main never received it because the back-sync (core#27) is blocked behind CI.What this PR does
Cherry-picks
1d8c101conto main directly. 8 files changed, all 1d8c101c-only:.github/workflows/codeql.yml.github/workflows/harness-replays.yml.github/workflows/publish-workspace-server-image.yml(the urgent one)workspace-server/Dockerfile+Dockerfile.tenantworkspace-server/cmd/server/main.goworkspace-server/go.mod+go.sumLocal verify: all YAML files parse, plugin checkout step is removed, diff stat matches PR#23 exactly.
CI expectation
After merge:
publish-workspace-server-image.ymlon the new main HEAD will succeed → ECRmolecule-ai/platform:staging-<sha>+:staging-latestget fresh push.molecule-ai/platform-tenant.Any CI red on this PR for unrelated stuff (Class H test bleed, CodeQL ×3 parked, Harness Replays Class G parked) is expected per the orchestrator-acked CI freeze and not a blocker per Hongming directive.
Orchestrator decision-locked option (b) cherry-pick path 2026-05-07 14:45.
Merge with merge commit (NOT squash) per saved memory feedback_use_merge_commits_not_squash.
Two coupled cleanups for the post-2026-05-06 stack: ============================================ The plugin injected GITHUB_TOKEN/GH_TOKEN via the App's installation-access flow (~hourly rotation). Per-agent Gitea identities replaced this approach after the 2026-05-06 suspension — workspaces now provision with a per-persona Gitea PAT from .env instead of an App-rotated token. The plugin code itself lived on github.com/Molecule-AI/molecule-ai-plugin-github-app-auth which is also unreachable post-suspension; checking it out at CI build time was already failing. Removed: - workspace-server/cmd/server/main.go: githubappauth import + the `if os.Getenv("GITHUB_APP_ID") != ""` block that called BuildRegistry. gh-identity remains as the active mutator. - workspace-server/Dockerfile + Dockerfile.tenant: COPY of the sibling repo + the `replace github.com/Molecule-AI/molecule-ai- plugin-github-app-auth => /plugin` directive injection. - workspace-server/go.mod + go.sum: github-app-auth dep entry (cleaned up by `go mod tidy`). - 3 workflows: actions/checkout steps for the sibling plugin repo: - .github/workflows/codeql.yml (Go matrix path) - .github/workflows/harness-replays.yml - .github/workflows/publish-workspace-server-image.yml Verified `go build ./cmd/server` + `go vet ./...` pass post-removal. ======================================================= Same workflow used to push to ghcr.io/molecule-ai/platform + platform-tenant. ghcr.io/molecule-ai is gone post-suspension. The operator's ECR org (153263036946.dkr.ecr.us-east-2.amazonaws.com/ molecule-ai/) already hosts platform-tenant + workspace-template-* + runner-base images and is the post-suspension SSOT for container images. This PR aligns publish-workspace-server-image with that stack. - env.IMAGE_NAME + env.TENANT_IMAGE_NAME repointed to ECR URL. - docker/login-action swapped for aws-actions/configure-aws- credentials@v4 + aws-actions/amazon-ecr-login@v2 chain (the standard ECR auth pattern; uses AWS_ACCESS_KEY_ID/SECRET secrets bound to the molecule-cp IAM user). The :staging-<sha> + :staging-latest tag policy is unchanged — staging-CP's TENANT_IMAGE pin still points at :staging-latest, just with the new registry prefix. Refs molecule-core#157, #161; parallel to org-wide CI-green sweep.