-
Notifications
You must be signed in to change notification settings - Fork 156
chore: migrate to pnpm #1137
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: migrate to pnpm #1137
Conversation
Signed-off-by: Tomás Migone <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot reviewed 47 out of 53 changed files in this pull request and generated no comments.
Files not reviewed (6)
- .yarnrc.yml: Language not supported
- package.json: Language not supported
- packages/contracts/package.json: Language not supported
- packages/contracts/scripts/analyze: Language not supported
- packages/contracts/scripts/build: Language not supported
- packages/contracts/scripts/coverage: Language not supported
Comments suppressed due to low confidence (2)
.github/workflows/build.yml:25
- The fallback command 'pnpm build || pnpm build' appears redundant. Consider using a single 'pnpm build' command to improve clarity.
pnpm build || pnpm build
.github/workflows/verifydeployed.yml:36
- The use of 'pnpm build || pnpm build' is redundant; using 'pnpm build' alone should suffice unless a fallback is explicitly needed.
pnpm build || pnpm build
🚨 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 a critical CVE?Contains a Critical Common Vulnerability and Exposure (CVE). Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. 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
|
chore: migrate to pnpm
🚨 Report Summary
For more details view the full report in OpenZeppelin Code Inspector |
No description provided.