-
Notifications
You must be signed in to change notification settings - Fork 26.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: update pnpm@9.0.5 #64854
chore: update pnpm@9.0.5 #64854
Conversation
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
2 similar comments
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is an install script?Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts. Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
@ryota-murakami Looks like there is a conflict with the lock file |
@samcx Yeah, but got |
@ryota-murakami I just created a new |
Here are the release notes for PNPM from v9.0.0 to v9.0.5:
Notable change of v9 is Corepack enable by default.
So we can ensure all package manage/resolved exact same version of pnpm.
v9.0.0: Discontinued support for Node.js v16 and introduced Corepack compatibility checks. New configuration updates include enabling
dedupe-injected-deps
and changing the lockfile to version 9, with better readability and resistance to Git conflicts.v9.0.1: Resolved issues with
pnpm install --frozen-lockfile
, allowing it to work with lockfiles generated by PNPM v8 if no updates are required.v9.0.2: Addressed a bug where optional dependencies were not linked into dependent's
node_modules
. Fixed some other minor bugs.v9.0.3: Implemented changes to address the
script-shell
option erroring on Windows with.bat
or.cmd
files. Also fixed issues withpackage-manager-strict
checks and added more completion command support.v9.0.4: Fixed aliased dependencies resolution on repeated installs with existing lockfiles and addressed issues with
engines.pnpm
field in package.json being ignoredv9.0.5