Skip to content

chore: upgrade yarn to 4.17.1 and replace constraints.pro with yarn.config.cjs - #314

Open
cryptodev-2s wants to merge 3 commits into
chore/bump-nodefrom
chore/upgrade-yarn
Open

cryptodev-2s wants to merge 3 commits into
chore/bump-nodefrom
chore/upgrade-yarn

Conversation

@cryptodev-2s

@cryptodev-2s cryptodev-2s commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

Upgrades Yarn to 4.17.1 and replaces constraints.pro with a yarn.config.cjs.

@socket-security

socket-security Bot commented Nov 11, 2026 •

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Added@​yarnpkg/​types@​4.0.11001006682100

View full report

@socket-security

socket-security Bot commented Nov 11, 2026 •

Copy link
Copy Markdown

Caution

MetaMask internal reviewing guidelines:

  • Do not ignore-all
  • Each alert has instructions on how to review if you don't know what it means. If lost, ask your Security Liaison or the supply-chain group
  • Copy-paste ignore lines for specific packages or a group of one kind with a note on what research you did to deem it safe.
    @SocketSecurity ignore npm/PACKAGE@VERSION
Priority Alert  (click "▶" to expand/collapse) Action
Low priority
Publisher changed: npm tslib is now published by microsoft1es

Author: microsoft1es

From: package.json → npm/@yarnpkg/types@4.0.1 → npm/tslib@2.9.1

ℹ Read more on: This package | This alert | What is unstable ownership?

Next steps: Take 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@socket.dev.

Suggestion: Try to reduce the number of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/tslib@2.9.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block
Low priority
Publisher changed: npm tslib is now published by microsoft1es instead of typescript-bot

New Author: microsoft1es

Previous Author: typescript-bot

From: package.json → npm/@yarnpkg/types@4.0.1 → npm/tslib@2.9.1

ℹ Read more on: This package | This alert | What is new author?

Next steps: Take 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@socket.dev.

Suggestion: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/tslib@2.9.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block

View full report

@cryptodev-2s
cryptodev-2s added this pull request to stack #319 November 11, 2026 21:12
@cryptodev-2s
cryptodev-2s marked this pull request as ready for review November 12, 2026 10:10
@cryptodev-2s cryptodev-2s self-assigned this Nov 12, 2026
@cursor

cursor Bot commented Nov 12, 2026

Copy link
Copy Markdown

This PR is too large for Bugbot to review. It changes 1,155 lines and 4,188,914 characters. Split the change into smaller pull requests to get a review.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant