fix(infra): use --legacy flag for pnpm deploy in server Dockerfile - #23
Open
iis-MarkKuang wants to merge 1 commit into
Open
fix(infra): use --legacy flag for pnpm deploy in server Dockerfile#23iis-MarkKuang wants to merge 1 commit into
iis-MarkKuang wants to merge 1 commit into
Conversation
pnpm v10 no longer deploys workspaces without inject-workspace-packages, breaking `docker compose up` at the server build step with ERR_PNPM_DEPLOY_NONINJECTED_WORKSPACE. Pass --legacy to restore the pre-v10 deploy behavior so the prod image build succeeds. Co-authored-by: Cursor <cursoragent@cursor.com>
iis-MarkKuang
force-pushed
the
fix/infra-pnpm-deploy-legacy
branch
from
June 9, 2026 12:36
a281fb6 to
4ef65c9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docker compose upfails at the server image build step with:The repo pins pnpm 10 (
packageManager: "pnpm@10.30.3"), and in pnpm v10pnpm deployno longer copies workspace packages unless they opt in viainject-workspace-packages=true. Since@open-managed-agents/serverdepends on@open-managed-agents/types(workspace:*), the prod-image build step exits 1 and the whole stack fails to come up.This passes the
--legacyflag to restore pnpm's pre-v10 deploy behavior, which is the minimal, low-risk fix.Why this slipped through CI
The
docker-composeCI job only validates thatdocker-compose.ymlparses and declares the expected services — it does not build the images, so this pnpm v10 regression wasn't caught.Test plan
docker compose build servercompletes withoutERR_PNPM_DEPLOY_NONINJECTED_WORKSPACEdocker compose up -dbrings up postgres + server + web, all healthycurl http://localhost:3001/healthreturns 200Notes / follow-ups
inject-workspace-packages=trueinpackages/server/package.json;--legacywas chosen as the smaller change.docker-composeCI job so future build regressions are caught.