Bump MetaMask dependencies #351
Conversation
|
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@metamask/[email protected], npm/@metamask/[email protected], npm/@metamask/[email protected], npm/@metamask/[email protected], npm/@metamask/[email protected], npm/@metamask/[email protected], npm/@metamask/[email protected] |
|
👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎ This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. Ignoring: Next stepsTake 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 |
|
@SocketSecurity ignore npm/@metamask/[email protected] This is ours. |
….0.2` (#5080) ## Explanation This bumps `@metamask/utils` from `^10.0.0` to `^11.0.1`, in an effort to bump all packages using `@metamask/utils` to use v11. Unfortunately there are some circular dependencies, so this does not completely eliminate previous versions yet, but this is required to bump `@metamask/utils` in other packages, such as: - MetaMask/eth-json-rpc-middleware#351 ## Changelog <!-- If you're making any consumer-facing changes, list those changes here as if you were updating a changelog, using the template below as a guide. (CATEGORY is one of BREAKING, ADDED, CHANGED, DEPRECATED, REMOVED, or FIXED. For security-related issues, follow the Security Advisory process.) Please take care to name the exact pieces of the API you've added or changed (e.g. types, interfaces, functions, or methods). If there are any breaking changes, make sure to offer a solution for consumers to follow once they upgrade to the changes. Finally, if you're only making changes to development scripts or tests, you may replace the template below with "None". --> - **CHANGED**: Bump `@metamask/utils` from `^10.0.0` to `^11.0.1` - **CHANGED**: Bump `@metamask/rpc-errors` from `^7.0.1` to `^7.0.2` ## Checklist - [x] I've updated the test suite for new or updated code as appropriate - [x] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate - [x] I've highlighted breaking changes using the "BREAKING" category above as appropriate - [x] I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes
This contains the following bumps:
@metamask/eth-block-trackerfrom^11.0.3to^11.0.4.@metamask/eth-json-rpc-providerfrom^4.1.5to^4.1.7.@metamask/eth-sig-utilfrom^7.0.3to^8.1.2.@metamask/json-rpc-enginefrom^10.0.0to^10.0.2.@metamask/rpc-errorsfrom^7.0.0to^7.0.2.@metamask/utilsfrom^9.1.0to^11.0.1.This removes previous major versions of
@metamask/utilsfrom the dependency tree.