Build(deps): Bump @metamask/utils from 11.12.1 to 12.0.0

[dependabot]

Bumps @metamask/utils from 11.12.1 to 12.0.0.

Release notes

Sourced from @​metamask/utils's releases.

12.0.0

Changed

• BREAKING: Bump TypeScript target to ES2022 (#333)
  • This package now ships ES2022 code, requiring a compatible modern environment or bundler configuration to consume.
• BREAKING: Drop support for Node 18 and 20 (#328)
• BREAKING: Drop CommonJS support (#9536)
  • This package is now ESM-only, but can still be used in CommonJS projects via require(esm) in modern Node.js versions (22+), or dynamic imports in older Node.js versions.
• Bump @ethereumjs/tx from ^4.2.0 to ^5.4.0 (#321)
  • The deprecated Keyring.signTransaction now returns LegacyTxData rather than TxData. These describe the same shape: @ethereumjs/tx@5 repurposed the name TxData for a map keyed by transaction type and renamed the old meaning to LegacyTxData. Implementations do not need changing.
• Bump @metamask/scure-bip39 from ^2.0.3 to ^2.1.1 (#311)
• Bump @metamask/superstruct from ^3.1.0 to ^3.4.1 (#311)
• Bump @noble/hashes from ^1.3.1 to ^1.8.0 (#311)
• Bump @scure/base from ^1.1.3 to ^1.2.6 (#311)
• Bump semver from ^7.5.4 to ^7.6.3 (#311)

Changelog

Sourced from @​metamask/utils's changelog.

[12.0.0]

Changed

• BREAKING: Bump TypeScript target to ES2022 (#333)
  • This package now ships ES2022 code, requiring a compatible modern environment or bundler configuration to consume.
• BREAKING: Drop support for Node 18 and 20 (#328)
• BREAKING: Drop CommonJS support (#9536)
  • This package is now ESM-only, but can still be used in CommonJS projects via require(esm) in modern Node.js versions (22+), or dynamic imports in older Node.js versions.
• Bump @ethereumjs/tx from ^4.2.0 to ^5.4.0 (#321)
  • The deprecated Keyring.signTransaction now returns LegacyTxData rather than TxData. These describe the same shape: @ethereumjs/tx@5 repurposed the name TxData for a map keyed by transaction type and renamed the old meaning to LegacyTxData. Implementations do not need changing.
• Bump @metamask/scure-bip39 from ^2.0.3 to ^2.1.1 (#311)
• Bump @metamask/superstruct from ^3.1.0 to ^3.4.1 (#311)
• Bump @noble/hashes from ^1.3.1 to ^1.8.0 (#311)
• Bump @scure/base from ^1.1.3 to ^1.2.6 (#311)
• Bump semver from ^7.5.4 to ^7.6.3 (#311)

Commits

• 94b19fb 12.0.0 (#339)
• 212cb5c chore: type check tests via lint:tsc (#334)
• 358c630 chore!: bump TypeScript target and lib to ES2022 (#333)
• baa6dad chore: adopt core's TypeScript 6 and 7 arrangement (#325)
• 0c93a38 feat!: convert the package to ESM only (#323)
• 1de19fa feat!: drop support for Node 18 and 20 (#328)
• d65c1c1 chore: replace depcheck with knip (#330)
• 106371c fix: make the tsd type tests actually run (#322)
• 300b7c1 chore: bump @ethereumjs/tx to v5 (#321)
• b665d7b chore: bump Jest to v30 (#319)
• Additional commits viewable in compare view

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​metamask/​utils@​11.12.1 ⏵ 12.0.0			+7	+2

View full report

[socket-security]

Warning

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
	Network access: npm @ethereumjs/util in module globalThis["fetch"] Module: globalThis["fetch"] Location: Package overview From: package.json → npm/@metamask/utils@12.0.0 → npm/@ethereumjs/util@9.1.0 ℹ Read more on: This package | This alert | What is network access? 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: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@ethereumjs/util@9.1.0. 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.	Warn

View full report