Skip to content

fix(ci): clone sibling plugin repo so publish-workspace-server-image builds - #996

Merged
HongmingWang-Rabbit merged 1 commit into
stagingfrom
fix/publish-clone-plugin-sibling
Apr 19, 2026
Merged

HongmingWang-Rabbit merged 1 commit into
stagingfrom
fix/publish-clone-plugin-sibling

Conversation

@HongmingWang-Rabbit

Copy link
Copy Markdown
Contributor

Summary

Publish has been broken since the 2026-04-18 open-source restructure. `workspace-server/Dockerfile` still `COPY`s `./molecule-ai-plugin-github-app-auth/` but the restructure moved that plugin to its own repo. Every main merge since has failed at "failed to compute cache key: `/molecule-ai-plugin-github-app-auth`: not found" — meaning prod tenant images haven't been rebuilt for days. This is why the Phase 1.5 / canary / billing-gate merges didn't reach the tenant image fleet yet.

Fix

Add an `actions/checkout` step that fetches the plugin repo into the build context before `docker build` runs.

Ops action required before next main merge

The plugin repo is private. Add a fine-grained PAT as a repo secret:

  1. GitHub → Settings → Developer settings → Personal access tokens → Fine-grained
  2. Repository access: `Molecule-AI/molecule-ai-plugin-github-app-auth` only
  3. Permissions: Contents: Read
  4. Copy token → `Molecule-AI/molecule-core` → Settings → Secrets → Actions → new secret `PLUGIN_REPO_PAT`

The workflow falls back to the default `GITHUB_TOKEN` if the secret is missing — so if the plugin repo is ever made public, it keeps working without the PAT.

Test plan

  • Workflow YAML is valid
  • After merging + setting `PLUGIN_REPO_PAT`: confirm next main merge publishes `:staging-`
  • Manually retag `:staging-` → `:latest` via `scripts/rollback-latest.sh ` (canary isn't live yet, so the automatic gate doesn't promote)

🤖 Generated with Claude Code

…builds

Publish has been failing since the 2026-04-18 open-source restructure
(#964's merge) because workspace-server/Dockerfile still COPYs
./molecule-ai-plugin-github-app-auth/ but the restructure moved that
code out to its own repo. Every main merge since has produced a
"failed to compute cache key: /molecule-ai-plugin-github-app-auth:
not found" error — prod images haven't moved.

Fix: add an actions/checkout step that fetches the plugin repo into
the build context before docker build runs.

Private-repo safe: uses PLUGIN_REPO_PAT secret (fine-grained PAT with
Contents:Read on Molecule-AI/molecule-ai-plugin-github-app-auth).
Falls back to the default GITHUB_TOKEN if the plugin repo is public.

Ops: set repo secret PLUGIN_REPO_PAT before the next main merge, or
publish will fail with a 404 on the checkout step.

Also gitignores the cloned dir so local dev builds don't accidentally
commit it.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@HongmingWang-Rabbit
HongmingWang-Rabbit merged commit 526bb59 into staging Apr 19, 2026
6 of 9 checks passed
molecule-ai Bot pushed a commit that referenced this pull request Apr 21, 2026
…ling

fix(ci): clone sibling plugin repo so publish-workspace-server-image builds
@HongmingWang-Rabbit
HongmingWang-Rabbit deleted the fix/publish-clone-plugin-sibling branch April 24, 2026 00:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant