Release 58.0.0

[MajorLift]

Explanation

This is the release candidate for v58.0.0.

• @metamask/[email protected] (patch)
• @metamask/[email protected] (patch)
• @metamask/[email protected] (patch)
• @metamask/[email protected] (patch)

Notes

• Removes @metamask/utils yarn resolution to 9.1.0.
• Bumps @metamask/eth-json-rpc-middleware from ^12.1.2 to ^13.0.0 in @metamask/snaps-{jest,simulator}.
• The permission-controller major version bump doesn't affect the snaps monorepo as a breaking change, as the updated enums CaveatMutatorOperations, MethodNames are not used in any snaps package.

Blockers

• Blocked by Fix regressions introduced by @metamask/[email protected] #2579: With yarn resolution for @metamask/utils removed, @metamask/snaps-execution-environments experiences a build error due to version mismatch between @metamask/providers (@metamask/[email protected]) and @metamask/[email protected].

  • Resolved with @metamask/[email protected]

• With @metamask/[email protected]

➤ YN0000: [@metamask/snaps-execution-environments]: src/common/BaseSnapExecutor.ts(373,23): error TS2322: Type 'import("/Users/majorlift/Code/metamask/snaps/node_modules/@metamask/json-rpc-engine/dist/types/JsonRpcEngine").JsonRpcMiddleware<import("/Users/majorlift/Code/metamask/snaps/node_modules/@metamask/utils/dist/json").JsonRpcParams, import("/Users/majorlift/Code/metamask/snaps/node_modules/@metamask/utils/dist/json").J...' is not assignable to type 'import("/Users/majorlift/Code/metamask/snaps/node_modules/@metamask/providers/node_modules/@metamask/json-rpc-engine/dist/types/JsonRpcEngine").JsonRpcMiddleware<import("/Users/majorlift/Code/metamask/snaps/node_modules/@metamask/providers/node_modules/@metamask/utils/dist/json").JsonRpcParams, import("/Users/majorl...'.
➤ YN0000: [@metamask/snaps-execution-environments]:   Types of parameters 'req' and 'req' are incompatible.
➤ YN0000: [@metamask/snaps-execution-environments]:     Type 'import("/Users/majorlift/Code/metamask/snaps/node_modules/@metamask/providers/node_modules/@metamask/utils/dist/json").JsonRpcRequest<import("/Users/majorlift/Code/metamask/snaps/node_modules/@metamask/providers/node_modules/@metamask/utils/dist/json").JsonRpcParams>' is not assignable to type 'import("/Users/majorlift/Code/metamask/snaps/node_modules/@metamask/utils/dist/json").JsonRpcRequest<import("/Users/majorlift/Code/metamask/snaps/node_modules/@metamask/utils/dist/json").JsonRpcParams>'.
➤ YN0000: [@metamask/snaps-execution-environments]:       Type 'JsonRpcRequest<JsonRpcParams>' is not assignable to type '{ params?: ((Record<string, Json> | Json[]) & ExactOptionalGuard) | undefined; id: string | number | null; method: string; jsonrpc: "2.0"; }'.
➤ YN0000: [@metamask/snaps-execution-environments]:         Types of property 'params' are incompatible.
➤ YN0000: [@metamask/snaps-execution-environments]:           Type '(((Record<string, Json> | Json[]) & ExactOptionalGuard) & JsonRpcParams) | undefined' is not assignable to type '((Record<string, Json> | Json[]) & ExactOptionalGuard) | undefined'.
➤ YN0000: [@metamask/snaps-execution-environments]:             Type 'Record<string, Json> & ExactOptionalGuard' is not assignable to type '((Record<string, Json> | Json[]) & ExactOptionalGuard) | undefined'.
➤ YN0000: [@metamask/snaps-execution-environments]:               Type 'Record<string, Json> & ExactOptionalGuard' is not assignable to type 'Json[] & ExactOptionalGuard'.
➤ YN0000: [@metamask/snaps-execution-environments]:                 Type 'Record<string, Json> & ExactOptionalGua

• With yarn resolution entry "@metamask/snaps-execution-environments/@metamask/providers": "17.1.1"

➤ YN0000: [@metamask/snaps-execution-environments]: node_modules/@metamask/providers/dist/EIP6963.d.cts(11,9): error TS2717: Subsequent property declarations must have the same type.  Property '[EIP6963EventNames.Request]' must be of type 'EIP6963RequestProviderEvent', but here has type 'EIP6963RequestProviderEvent'.
➤ YN0000: [@metamask/snaps-execution-environments]: node_modules/@metamask/providers/dist/EIP6963.d.cts(12,9): error TS2717: Subsequent property declarations must have the same type.  Property '[EIP6963EventNames.Announce]' must be of type 'EIP6963AnnounceProviderEvent', but here has type 'EIP6963AnnounceProviderEvent'.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.00%. Comparing base (223878c) to head (0d72427).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2595   +/-   ##
=======================================
  Coverage   94.00%   94.00%           
=======================================
  Files         459      459           
  Lines        9650     9650           
  Branches     1482     1482           
=======================================
  Hits         9071     9071           
  Misses        579      579           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@metamask/[email protected]	network	+10	1.02 MB	metamaskbot
npm/@noble/[email protected]	None	0	1.3 MB	paulmillr
npm/@scure/[email protected]	None	0	77.8 kB	paulmillr
npm/@scure/[email protected]	None	0	55.7 kB	paulmillr
npm/@scure/[email protected]	None	0	357 kB	paulmillr
npm/@types/[email protected]	None	0	7.22 kB	types
npm/@types/[email protected]	None	0	2.88 kB	types
npm/[email protected]	None	0	84.3 kB	paulmillr

🚮 Removed packages: npm/@metamask/[email protected], npm/@scure/[email protected]

View full report↗︎

[socket-security]

👍 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: npm/@metamask/[email protected]

View full report↗︎

Next steps

Take a deeper look at the dependency

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 [AT] socket [DOT] dev.

Remove the package

If 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 risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

[MajorLift]

@SocketSecurity ignore npm/@metamask/[email protected]
MetaMask package