chore(deps): bump @metamask/utils from 8.3.0 to 8.5.0

[dependabot]

Bumps @metamask/utils from 8.3.0 to 8.5.0.

Release notes

Sourced from @​metamask/utils's releases.

8.5.0

Changed

• Bump dependency semver from ^5.7.1 to ^7.6.0 (#181).

Fixed

• Replace dependency superstruct ^1.0.3 with ESM-compatible @metamask/superstruct ^3.0.0 (#185).
  • This fixes the issue of this package being unusable by any TypeScript project that uses Node16 or NodeNext as its moduleResolution option.
• Produce and export ESM-compatible TypeScript type declaration files in addition to CommonJS-compatible declaration files (#182)
  • Previously, this package shipped with only one variant of type declaration files, and these files were only CommonJS-compatible, and the exports field in package.json linked to these files. This is an anti-pattern and was rightfully flagged by the "Are the Types Wrong?" tool as "masquerading as CJS". All of the ATTW checks now pass.
• Remove chunk files (#182).
  • Previously, the build tool we used to generate JavaScript files extracted common code to "chunk" files. While this was intended to make this package more tree-shakeable, it also made debugging more difficult for our development teams. These chunk files are no longer present.

8.4.0

Added

• Add toCaipChainId utility function (#175)
• Add KnownCaipNamespace enum (#175)

Changed

• Update docs for createDeferredPromise to caution against using suppressUnhandledRejection (#174)

Fixed

• Fix createSandbox to assign a unique name to the sandbox directory, so that it can be used in multiple concurrently running Jest tests (#171)

Changelog

Sourced from @​metamask/utils's changelog.

[8.5.0]

Changed

• Bump dependency semver from ^5.7.1 to ^7.6.0 (#181).

Fixed

• Replace dependency superstruct ^1.0.3 with ESM-compatible @metamask/superstruct ^3.0.0 (#185).
  • This fixes the issue of this package being unusable by any TypeScript project that uses Node16 or NodeNext as its moduleResolution option.
• Produce and export ESM-compatible TypeScript type declaration files in addition to CommonJS-compatible declaration files (#182)
  • Previously, this package shipped with only one variant of type declaration files, and these files were only CommonJS-compatible, and the exports field in package.json linked to these files. This is an anti-pattern and was rightfully flagged by the "Are the Types Wrong?" tool as "masquerading as CJS". All of the ATTW checks now pass.
• Remove chunk files (#182).
  • Previously, the build tool we used to generate JavaScript files extracted common code to "chunk" files. While this was intended to make this package more tree-shakeable, it also made debugging more difficult for our development teams. These chunk files are no longer present.

[8.4.0]

Added

• Add toCaipChainId utility function (#175)
• Add KnownCaipNamespace enum (#175)

Changed

• Update docs for createDeferredPromise to caution against using suppressUnhandledRejection (#174)

Fixed

• Fix createSandbox to assign a unique name to the sandbox directory, so that it can be used in multiple concurrently running Jest tests (#171)

Commits

• c72216b 8.5.0 (#191)
• 631d1eb Use @metamask/superstruct, set moduleResolution to NodeNext (#185)
• 7eac3c8 Bump semver (#181)
• 1c408dd Use ts-bridge for building (#182)
• e122e33 Bump tar from 6.1.11 to 6.2.1 (#180)
• 665d0bc 8.4.0 (#176)
• d532b07 feat(caip): add .toCaipChainId + KnownCaipNamespace (#175)
• e58a8d8 docs: Add caution about suppressing errors (#174)
• 588f267 Update security code scanner file (#172)
• aff049e Enabling MetaMask security code scanner (#170)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[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

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Medium CVE: npm uuid: Missing buffer bounds check in v3/v5/v6 when buf is provided CVE: GHSA-w5hq-g745-h8pq uuid: Missing buffer bounds check in v3/v5/v6 when buf is provided (MODERATE) Affected versions: < 14.0.0 Patched version: 14.0.0 From: ? → npm/@metamask/post-message-stream@8.0.0 → npm/uuid@9.0.1 ℹ Read more on: This package | This alert | What is a medium CVE? 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: Remove or replace dependencies that include known medium severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/uuid@9.0.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.

View full report