Conversation
Switch workspace installation and automation from npm to pnpm 11.5.0, add PNPM supply-chain protections, and convert internal package dependencies to workspace protocol.
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.
What is this?
This PR migrates the monorepo from npm workspaces to PNPM 11.5.0. It replaces the npm lockfiles with a single PNPM lockfile, adds
websiteto the PNPM workspace, and updates repo scripts, CI, and deployment automation to use PNPM.How does it work?
The root now declares
pnpm@11.5.0and usespnpm-workspace.yamlfor workspace membership and security settings. Internal Voltra package dependencies use theworkspace:protocol, while CI installs dependencies withpnpm install --frozen-lockfile. The website deploy flow uses the locked Vercel CLI dependency instead of installingvercel@latestglobally.Why is this useful?
This makes package resolution consistent across the monorepo, ensures local package dependencies resolve through the workspace, and protects installs from newly published package versions by requiring a 14-day minimum release age. The explicit build-script allowlist also keeps dependency lifecycle scripts visible and intentional.