ci: upgrade pnpm to 11#6367
Merged
Merged
Conversation
pnpm 11 no longer reads the "pnpm" field in package.json, so add the security overrides to pnpm-workspace.yaml (where pnpm 10+ reads them) and switch the build-script allowlist to allowBuilds. The overrides are kept in package.json too because Vercel deploys still run pnpm 9 (the default for a lockfileVersion 9.0 lockfile when Corepack is off), which only reads them from there. Exclude our own @parca/* packages from pnpm 11's 24h release-age delay. CI reads the version from packageManager via action-setup@v6 instead of a pinned PNPM_VERSION env var.
|
✅ Meticulous spotted 0 visual differences across 267 screens tested: view results. Meticulous evaluated ~4 hours of user flows against your PR. Expected differences? Click here. Last updated for commit |
manojVivek
approved these changes
Jun 9, 2026
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
2 participants
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.
NixOS is dropping the older pnpm packages, so this moves us to pnpm 11. The non-obvious part is that pnpm 11 stopped reading the
pnpmfield inpackage.json, which meant our security overrides were silently ignored andpnpm install --frozen-lockfilefailed on a config mismatch. They now live inpnpm-workspace.yamlalongside theallowBuildsallowlist, with@parca/*excluded from pnpm 11's 24h release-age delay, and CI reads the version frompackageManagerviaaction-setup@v6instead of a pinned env var.