Docker builds fail since the audit commit (d6f52d1) with ERR_PNPM_LOCKFILE_CONFIG_MISMATCH. The audit moved overrides into pnpm-workspace.yaml and relocked, but the Dockerfile never copied that file. It wrote its own containing only packages:, so pnpm saw no overrides while the lockfile had them.
The same commit bumped pnpm to 12, which no longer reads the "pnpm" field in package.json. That silently dropped patchedDependencies from the lockfile, so the mobile patches were no longer applied.
Fix
Both install stages copy the real pnpm-workspace.yaml. Mobile still stays out because its manifest is never copied, so the apps/* glob can't find it (install scope is still "2 of 3 workspace projects").
patchedDependencies moved from package.json into pnpm-workspace.yaml and relocked. The lockfile has its patch hashes again.
Docker builds fail since the audit commit (`d6f52d1`) with `ERR_PNPM_LOCKFILE_CONFIG_MISMATCH`. The audit moved `overrides` into `pnpm-workspace.yaml` and relocked, but the Dockerfile never copied that file. It wrote its own containing only `packages:`, so pnpm saw no overrides while the lockfile had them.
The same commit bumped pnpm to 12, which no longer reads the `"pnpm"` field in `package.json`. That silently dropped `patchedDependencies` from the lockfile, so the mobile patches were no longer applied.
**Fix**
- Both install stages copy the real `pnpm-workspace.yaml`. Mobile still stays out because its manifest is never copied, so the `apps/*` glob can't find it (install scope is still "2 of 3 workspace projects").
- `patchedDependencies` moved from `package.json` into `pnpm-workspace.yaml` and relocked. The lockfile has its patch hashes again.
Verified with a full local `docker build`.
---
Changes made by Claude Opus 5.5 via Claude Code.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The pnpm 12 audit moved overrides into pnpm-workspace.yaml, but the
Dockerfile wrote its own workspace file, so frozen installs failed with
ERR_PNPM_LOCKFILE_CONFIG_MISMATCH. pnpm 12 also ignores the "pnpm" field
in package.json, which silently dropped the mobile patches, so they move
to the workspace file too.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Docker builds fail since the audit commit (
d6f52d1) withERR_PNPM_LOCKFILE_CONFIG_MISMATCH. The audit movedoverridesintopnpm-workspace.yamland relocked, but the Dockerfile never copied that file. It wrote its own containing onlypackages:, so pnpm saw no overrides while the lockfile had them.The same commit bumped pnpm to 12, which no longer reads the
"pnpm"field inpackage.json. That silently droppedpatchedDependenciesfrom the lockfile, so the mobile patches were no longer applied.Fix
pnpm-workspace.yaml. Mobile still stays out because its manifest is never copied, so theapps/*glob can't find it (install scope is still "2 of 3 workspace projects").patchedDependenciesmoved frompackage.jsonintopnpm-workspace.yamland relocked. The lockfile has its patch hashes again.Verified with a full local
docker build.Changes made by Claude Opus 5.5 via Claude Code.
🤖 Generated with Claude Code