Bump @metamask/snaps-utils from 10.1.0 to 11.1.0

[dependabot]

Bumps @metamask/snaps-utils from 10.1.0 to 11.1.0.

Commits

• 75c8329 release: 119.0.0 (#3533)
• 23bbcf9 feat: Allow all children in Row (#3532)
• 304ada7 fix: Display CLI minimum version range (#3531)
• 56aaed7 feat: Add non-fungible assets support to endowment:assets (#3527)
• 27f8e10 chore: Bump @​metamask/controller-utils from 11.10.0 to 11.11.0 (#3529)
• 48783d9 fix: Add snap metadata to simulation accounts (#3528)
• 20ed5ef feat: Add feature flag to treat local Snaps as preinstalled (#3523)
• 285c8d8 chore: Bump @​metamask/rpc-errors from 7.0.2 to 7.0.3 (#3525)
• 8f60fb9 chore: Bump @​metamask/utils from 11.4.1 to 11.4.2 (#3526)
• f56d0dd release: 118.0.0 (#3524)
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action	Severity	Alert (click for details)
Block		@metamask/snaps-sdk@9.2.0 has Network access. Module: globalThis["fetch"] Location: Package overview From: yarn.lock → npm/@metamask/snaps-sdk@9.2.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/@metamask/snaps-sdk@9.2.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.
Block		@metamask/snaps-utils@11.1.0 has Network access. Module: globalThis["fetch"] Location: Package overview From: yarn.lock → npm/@metamask/snaps-utils@11.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/@metamask/snaps-utils@11.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.

View full report

[cursor]

Bug: Dependency Conflict Causes Version Incompatibility

Upgrading @metamask/snaps-utils to ^11.1.0 introduces a version conflict with @metamask/snaps-sdk. The new snaps-utils requires snaps-sdk@^9.2.0, but the project directly depends on snaps-sdk@^8.1.0. This forces Yarn to install both major versions, leading to potential runtime errors, type conflicts, and unexpected behavior.

package.json#L46-L48

snaps-registry/package.json

Lines 46 to 48 in bd4c07e

	"@metamask/snaps-controllers": "^13.1.0",
	"@metamask/snaps-sdk": "^8.1.0",
	"@metamask/snaps-utils": "^11.1.0",

Fix in Cursor • Fix in Web

---

Was this report helpful? Give feedback by reacting with 👍 or 👎

[dependabot]

Superseded by #1284.