chore(deps): bump @metamask/snaps-sdk from 9.0.0 to 10.0.0

[dependabot]

Bumps @metamask/snaps-sdk from 9.0.0 to 10.0.0.

Commits

• 93f69e5 release: 126.0.0 (#3662)
• 604e87b chore!: Make interface actions synchronous (#3361)
• 8b4369d perf: Reduce JSON validation during state updates (#3660)
• 0c693f0 perf: Simplify JSON-RPC failure validation (#3661)
• 56e8b0a chore: Bump @​lavamoat/webpack from 1.2.0 to 1.5.0 (#3659)
• f3e64c7 feat!: Remove useCaip25Permission feature flag and enable behaviour by defa...
• 8571a4d perf: Move request inspection outside of the executor (#3356)
• 222928d chore: Bump @​metamask/eth-block-tracker from 12.0.1 to 12.1.0 (#3654)
• 36f2212 chore: Bump @​lavamoat/allow-scripts from 3.3.5 to 3.4.0 (#3651)
• a566abd chore: Fix broken coverage script (#3657)
• 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)

---

Note

Bumps @metamask/snaps-sdk to ^10.1.0 across multiple packages and updates lockfile sub-dependencies.

• Dependencies:
  • Upgrade @metamask/snaps-sdk to ^10.1.0 in packages/account-tree-controller, packages/accounts-controller, packages/assets-controllers, packages/gator-permissions-controller, packages/multichain-account-service, packages/multichain-transactions-controller, and packages/profile-sync-controller.
  • Update yarn.lock to include @metamask/providers@^22.1.1, @metamask/rpc-errors@^7.0.3, and expand @metamask/utils range to include ^11.4.2.

^{Written by Cursor Bugbot for commit f51c617. This will update automatically on new commits. Configure here.}

[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/​providers@​22.1.1

View full report

[cursor]

Bug: Dependency version clash with Snaps SDK peers

Bumping @metamask/snaps-sdk to ^10.1.0 creates a version conflict with peer dependency @metamask/snaps-controllers@^14.0.0 which still requires @metamask/snaps-sdk@^9.0.0. This causes both versions to be installed simultaneously, potentially leading to type conflicts, runtime errors from incompatible APIs, and increased bundle size. The same issue affects all packages in this diff that have @metamask/snaps-controllers as a peer dependency.

 

[cursor]

Bug: Dependency conflict from mixed Snap SDK versions

Bumping @metamask/snaps-sdk to ^10.1.0 while keeping @metamask/snaps-utils at ^11.0.0 creates a dependency conflict. The yarn.lock shows @metamask/snaps-utils@11.0.0 depends on @metamask/snaps-sdk@^9.0.0, causing both SDK versions to be installed. This major version mismatch can lead to runtime errors, type conflicts, and unexpected behavior since version 10.x includes breaking changes.