Pin the pnpm version for reproducible web installs #26
Reference in New Issue
Block a user
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?
Context
The
web/package has nopackageManagerfield, and the CIwebjob pins pnpm only at the major level (pnpm/action-setup@v4withversion: 9). Locally the lockfile was written with pnpm 11.5.1; both emitlockfileVersion: '9.0', so--frozen-lockfilepasses today — but the pnpm version is effectively unpinned and can drift between contributors and CI.What to do
"packageManager": "pnpm@<exact-version>"field toweb/package.json(Corepack reads it for a deterministic pnpm).webjob's pnpm version consistent with that pin (or rely on Corepack), so local and CI use the same pnpm.Acceptance
web/package.jsondeclares an exactpackageManagerpnpm version.pnpm install --frozen-lockfilestays green.Source: frontend SPA milestone 1 final review — reproducibility nit.