chore: upgrade pnpm to 11#975
Open
richadr wants to merge 2 commits into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
5 tasks
…h pnpm 11 as the default package manager)
|
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.
This PR upgrades pnpm to the latest version. pnpm 11 has been out for a while now, and is now the recommended version to use. Set the minimum version to 11.4 since that is the latest version with security fixes. To use pnpm 11, ensure you're on a recent version of Node and run
corepack enablein the root of the repository.pnpm 11 comes with breaking changes and the migration guide was used. It comes with better defaults for strictDepBuilds: you must now explicitly review which build scripts are allowed. As well as
blockExoticSubdeps.The automigration moved all properties from
.npmrctopnpm-workspace.yaml, but we want to keepignore-scriptsas a safety measure andprovenancebecause changeset publish bypasses pnpm.minimumReleaseAgeby default is now 24h, same as our existing setting. I still kept it inpnpm-workspace.yaml, as it doesn't hurt to be explicit about it.Also cleaned up the workaround in pipelines that allowed an RC version of pnpm to be used when the npm audit endpoint was down. With pnpm 11, this is no longer needed.