chore: upgrade to pnpm v11 and enhance security settings#361
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 focuses on updating package management tooling and enhancing security policies for dependency updates.
The main changes include upgrading the
pnpmpackage manager version, improving platform compatibility for native dependencies, and introducing stricter security controls for dependency updates.Dependency management and compatibility:
pnpmpackage manager version from10.27.0to11.7.0inpackage.jsonfor improved features and bug fixes.libcconstraints (eitherglibcormusl) to various nativesharpandsharp-libvipsdependencies inpnpm-lock.yaml, improving compatibility and reliability across different Linux distributions and architectures.Security and update policies:
pnpm-workspace.yaml, including:esbuildto prevent unwanted binary builds.