chore: bump `@metamask/{keyring-api,eth-snap-keyring,snaps-*}`

ccharly commented 2 days ago

Explanation

Updating accounts related packages. We do skip 1 major for the keyring-api which is ok:

9.0.0 was about Bitcoin changes (renaming the only BTC method we support)
10.1.0:
- bumps the @metamask/providers to the same version than the one expected by snaps-* packages and the eth-snap-keyring
- adds basic Solana support

References

N/A

Changelog

`@metamask/accounts-controller`

CHANGED: Bump keyring-api to ^10.1.0
CHANGED: Bump eth-snap-keyring to ^5.0.1
CHANGED: Bump snaps-utils to ^8.3.0
CHANGED: Bump snaps-sdk to ^6.7.0
CHANGED: Bump peer dependency snaps-controllers to ^9.10.0

`@metamask/assets-controllers`

CHANGED: Bump keyring-api to ^10.1.0

`@metamask/chain-controller`

CHANGED: Bump keyring-api to ^10.1.0
CHANGED: Bump snaps-utils to ^8.3.0
CHANGED: Bump snaps-sdk to ^6.7.0
CHANGED: Bump snaps-controllers to ^9.10.0

`@metamask/keyring-controller`

CHANGED: Bump keyring-api to ^10.1.0

`@metamask/profile-sync-controller`

CHANGED: Bump keyring-api to ^10.1.0
CHANGED: Bump snaps-utils to ^8.3.0
CHANGED: Bump snaps-sdk to ^6.7.0
CHANGED: Bump peer dependency snaps-controllers to ^9.10.0

`@metamask/transaction-controller`

CHANGED: Bump keyring-api to ^10.1.0

Checklist

[x] I've updated the test suite for new or updated code as appropriate
[x] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
[x] I've highlighted breaking changes using the "BREAKING" category above as appropriate
[x] I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes

socket-security[bot] commented 2 days ago

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

Package	New capabilities	Transitives	Size	Publisher
npm/@metamask/eth-snap-keyring@5.0.1	None	`+38`	7.65 MB	metamaskbot
npm/@metamask/keyring-api@10.1.0	None	`+10`	1.96 MB	metamaskbot

View full report↗︎

ccharly commented 2 days ago

@metamaskbot publish-previews

ccharly commented 2 days ago

@metamaskbot publish-previews

github-actions[bot] commented 2 days ago

Preview builds have been published. See these instructions for more information about preview builds.

Expand for full list of packages and versions.

``` { "@metamask-previews/accounts-controller": "19.0.0-preview-ff9209e", "@metamask-previews/address-book-controller": "6.0.1-preview-ff9209e", "@metamask-previews/announcement-controller": "7.0.1-preview-ff9209e", "@metamask-previews/approval-controller": "7.1.1-preview-ff9209e", "@metamask-previews/assets-controllers": "44.0.1-preview-ff9209e", "@metamask-previews/base-controller": "7.0.2-preview-ff9209e", "@metamask-previews/build-utils": "3.0.1-preview-ff9209e", "@metamask-previews/chain-controller": "0.1.3-preview-ff9209e", "@metamask-previews/composable-controller": "9.0.1-preview-ff9209e", "@metamask-previews/controller-utils": "11.4.3-preview-ff9209e", "@metamask-previews/ens-controller": "15.0.0-preview-ff9209e", "@metamask-previews/eth-json-rpc-provider": "4.1.6-preview-ff9209e", "@metamask-previews/gas-fee-controller": "22.0.1-preview-ff9209e", "@metamask-previews/json-rpc-engine": "10.0.1-preview-ff9209e", "@metamask-previews/json-rpc-middleware-stream": "8.0.5-preview-ff9209e", "@metamask-previews/keyring-controller": "18.0.0-preview-ff9209e", "@metamask-previews/logging-controller": "6.0.2-preview-ff9209e", "@metamask-previews/message-manager": "11.0.1-preview-ff9209e", "@metamask-previews/multichain": "0.0.0-preview-ff9209e", "@metamask-previews/name-controller": "8.0.1-preview-ff9209e", "@metamask-previews/network-controller": "22.0.2-preview-ff9209e", "@metamask-previews/notification-controller": "7.0.0-preview-ff9209e", "@metamask-previews/notification-services-controller": "0.13.0-preview-ff9209e", "@metamask-previews/permission-controller": "11.0.3-preview-ff9209e", "@metamask-previews/permission-log-controller": "3.0.1-preview-ff9209e", "@metamask-previews/phishing-controller": "12.3.0-preview-ff9209e", "@metamask-previews/polling-controller": "12.0.1-preview-ff9209e", "@metamask-previews/preferences-controller": "14.0.0-preview-ff9209e", "@metamask-previews/profile-sync-controller": "1.0.2-preview-ff9209e", "@metamask-previews/queued-request-controller": "7.0.1-preview-ff9209e", "@metamask-previews/rate-limit-controller": "6.0.1-preview-ff9209e", "@metamask-previews/selected-network-controller": "19.0.0-preview-ff9209e", "@metamask-previews/signature-controller": "22.0.0-preview-ff9209e", "@metamask-previews/transaction-controller": "39.0.0-preview-ff9209e", "@metamask-previews/user-operation-controller": "18.0.0-preview-ff9209e" } ```

ccharly commented 2 days ago

To add more context here, even though the @metamask/keyring-api new versions does require a new major version (18) of @metamask/providers, this is being "provided" (resolved?) by @metamask/snaps-sdk@6.10.0 which is the version we have our yarn.lock:

$ yarn why @metamask/providers -R
├─ @metamask/accounts-controller@workspace:packages/accounts-controller
│  ├─ @metamask/snaps-sdk@npm:6.10.0 (via npm:^6.7.0)
│  │  └─ @metamask/providers@npm:18.1.1 [66b24] (via npm:^18.1.1 [66b24])
│  ├─ @metamask/snaps-utils@npm:8.5.2 (via npm:^8.3.0)
│  │  └─ @metamask/snaps-sdk@npm:6.10.0 (via npm:^6.10.0)
│  ├─ @metamask/eth-snap-keyring@npm:5.0.1 [0a8f9] (via npm:^5.0.1 [0a8f9])
│  │  ├─ @metamask/snaps-sdk@npm:6.10.0 (via npm:^6.7.0)
│  │  ├─ @metamask/snaps-utils@npm:8.5.2 (via npm:^8.3.0)
│  │  └─ @metamask/snaps-controllers@npm:9.12.0 [0a8f9] (via npm:^9.10.0 [0a8f9])
│  │     ├─ @metamask/snaps-rpc-methods@npm:11.5.1 (via npm:^11.5.1)
│  │     │  ├─ @metamask/snaps-sdk@npm:6.10.0 (via npm:^6.10.0)
│  │     │  └─ @metamask/snaps-utils@npm:8.5.2 (via npm:^8.5.0)
│  │     ├─ @metamask/snaps-sdk@npm:6.10.0 (via npm:^6.10.0)
│  │     └─ @metamask/snaps-utils@npm:8.5.2 (via npm:^8.5.0)
│  └─ @metamask/keyring-api@npm:10.1.0 [8d095] (via npm:^10.1.0 [8d095])
│     └─ @metamask/snaps-sdk@npm:6.10.0 (via npm:^6.7.0)
│
├─ @metamask/assets-controllers@workspace:packages/assets-controllers
│  └─ @metamask/keyring-api@npm:10.1.0 [8d095] (via npm:^10.1.0 [8d095])
│
├─ @metamask/chain-controller@workspace:packages/chain-controller
│  ├─ @metamask/snaps-sdk@npm:6.10.0 (via npm:^6.7.0)
│  ├─ @metamask/snaps-utils@npm:8.5.2 (via npm:^8.3.0)
│  ├─ @metamask/keyring-api@npm:10.1.0 [8d095] (via npm:^10.1.0 [8d095])
│  └─ @metamask/snaps-controllers@npm:9.12.0 [0a8f9] (via npm:^9.10.0 [0a8f9])
│
├─ @metamask/keyring-controller@workspace:packages/keyring-controller
│  └─ @metamask/keyring-api@npm:10.1.0 [8d095] (via npm:^10.1.0 [8d095])
│
├─ @metamask/profile-sync-controller@workspace:packages/profile-sync-controller
│  ├─ @metamask/snaps-sdk@npm:6.10.0 (via npm:^6.7.0)
│  ├─ @metamask/snaps-utils@npm:8.5.2 (via npm:^8.3.0)
│  └─ @metamask/keyring-api@npm:10.1.0 [8d095] (via npm:^10.1.0 [8d095])
│
└─ @metamask/transaction-controller@workspace:packages/transaction-controller
   └─ @metamask/keyring-api@npm:10.1.0 [8d095] (via npm:^10.1.0 [8d095])

See:

│  ├─ @metamask/snaps-sdk@npm:6.10.0 (via npm:^6.7.0)
│  │  └─ @metamask/providers@npm:18.1.1 [66b24] (via npm:^18.1.1 [66b24])

Meaning, this @metamask/keyring-api is not breaking.

Also, see this reference to the yarn.lock:

https://github.com/MetaMask/core/pull/4948#discussion_r1850022205

MetaMask / core