chore: upgrade pnpm to v11#72
Merged
Merged
Conversation
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
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 updates package management tooling and tightens security policies for dependency management.
The main changes include upgrading the
pnpmpackage manager, updating key dependencies to newer versions, improving compatibility for native modules, and introducing stricter security and update policies in the workspace configuration.Dependency and Package Manager Updates:
pnpmpackage manager from version 10.7.0 to 11.8.0 inpackage.jsonfor improved performance and features.brace-expansiondependency from version 5.0.2 to 5.0.6 and theminimatchdependency from 10.2.1 to 10.2.5 inpnpm-lock.yamland their relevant snapshots, ensuring compatibility with Node.js 18 and above. [1] [2] [3] [4] [5]Native Module Compatibility:
libcfields (e.g.,glibc,musl) to several native module entries (such as@rolldown/binding-*andlightningcss-*) inpnpm-lock.yamlto improve platform-specific resolution and compatibility. [1] [2]Security and Update Policy Enhancements:
pnpm-workspace.yaml, including:esbuildminimumReleaseAge)blockExoticSubdeps)trustPolicy: "no-downgrade")