Skip to content

Conversation

@mathieuartu
Copy link
Contributor

@mathieuartu mathieuartu commented Mar 28, 2025

Description

This PR bumps @metamask/keyring-controller from ^19.2.2 to ^21.0.1
It also bumps packages that have @metamask/keyring-controller version ^21.0.0 as a peer dependency:

  • @metamask/accounts-controller to ^27.0.0
  • @metamask/approval-controller to ^7.1.3
  • @metamask/assets-controller to ^55.0.1
  • @metamask/bridge-controller to ^11.0.0
  • @metamask/bridge-status-controller to ^10.0.0
  • @metamask/controller-utils to ^11.6.0
  • @metamask/gas-fee-controller to ^23.0.0
  • @metamask/json-rpc-middleware-stream to ^8.0.7
  • @metamask/multichain-network-controller to ^0.3.0
  • @metamask/multichain-transactions-controller to ^0.8.0
  • @metamask/network-controller to ^23.1.0
  • @metamask/notification-services-controller to ^5.0.1
  • @metamask/phishing-controller to ^12.4.1
  • @metamask/preferences-controller to ^17.0.0
  • @metamask/profile-sync-controller to ^11.0.0
  • @metamask/selected-network-controller to ^22.0.0
  • @metamask/signature-controller to ^25.0.0
  • @metamask/transaction-controller to ^52.1.0

Related issues

(List WIP)
Fixes:

Manual testing steps

  1. No manual testing steps

Screenshots/Recordings

Before

After

Pre-merge author checklist

Pre-merge reviewer checklist

  • I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
  • I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

@mathieuartu mathieuartu added the team-identity-deprecated DEPRECATED: team no longer exists label Mar 28, 2025
@mathieuartu mathieuartu self-assigned this Mar 28, 2025
@github-actions
Copy link
Contributor

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

@socket-security
Copy link

socket-security bot commented Mar 28, 2025

New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@ethersproject/abstract-provider@5.8.0 Transitive: network +3 329 kB ricmoo
npm/@ethersproject/abstract-signer@5.8.0 None 0 82.2 kB ricmoo
npm/@ethersproject/address@5.8.0 None +4 333 kB ricmoo
npm/@ethersproject/base64@5.8.0 None 0 11.3 kB ricmoo
npm/@ethersproject/basex@5.8.0 None 0 30.1 kB ricmoo
npm/@ethersproject/constants@5.8.0 None 0 18.7 kB ricmoo
npm/@ethersproject/hash@5.8.0 None +2 407 kB ricmoo
npm/@ethersproject/hdnode@5.8.0 None 0 80.7 kB ricmoo
npm/@ethersproject/json-wallets@5.8.0 None +1 2.56 MB ricmoo
npm/@ethersproject/pbkdf2@5.8.0 None 0 17.4 kB ricmoo
npm/@ethersproject/random@5.8.0 None 0 17.3 kB ricmoo
npm/@ethersproject/sha2@5.8.0 None 0 21.7 kB ricmoo
npm/@ethersproject/signing-key@5.8.0 None 0 248 kB ricmoo
npm/@ethersproject/wallet@5.8.0 None 0 55.2 kB ricmoo
npm/@ethersproject/wordlists@5.8.0 None 0 390 kB ricmoo
npm/@metamask/accounts-controller@24.1.027.0.0 Transitive: network +2 1.14 MB metamaskbot
npm/@metamask/assets-controllers@51.0.255.0.1 None +5 3.8 MB metamaskbot
npm/@metamask/bridge-controller@7.0.011.0.0 None 0 445 kB metamaskbot
npm/@metamask/bridge-status-controller@7.0.010.0.0 None +1 540 kB metamaskbot
npm/@metamask/eth-json-rpc-infura@10.0.010.1.0 None 0 57.9 kB mcmire
npm/@metamask/eth-json-rpc-middleware@15.2.015.3.0 None 0 196 kB gudahtt
npm/@metamask/eth-snap-keyring@11.1.012.1.0 None +4 2.9 MB metamaskbot
npm/@metamask/gas-fee-controller@22.0.323.0.0 None 0 224 kB metamaskbot
npm/@metamask/keyring-controller@19.2.2, 21.0.021.0.1 Transitive: environment +2 713 kB metamaskbot
npm/@metamask/multichain-network-controller@0.1.10.3.0 None 0 111 kB metamaskbot
npm/@metamask/multichain-transactions-controller@0.7.20.8.0 None 0 94.1 kB metamaskbot
npm/@metamask/network-controller@22.2.123.1.0 None 0 866 kB metamaskbot
npm/@metamask/notification-services-controller@2.0.05.0.1 None 0 1.38 MB metamaskbot
npm/@metamask/polling-controller@13.0.0 None 0 99.3 kB metamaskbot
npm/@metamask/preferences-controller@15.0.117.0.0 None 0 141 kB metamaskbot
npm/@metamask/profile-sync-controller@10.1.011.0.0 None 0 1.14 MB metamaskbot
npm/@metamask/selected-network-controller@21.0.022.0.0 None 0 137 kB metamaskbot
npm/@metamask/signature-controller@23.1.027.0.0 None 0 316 kB metamaskbot
npm/@metamask/transaction-controller@45.0.052.1.0 None 0 2.45 MB metamaskbot

🚮 Removed packages: npm/@metamask/eth-simple-keyring@8.1.1, npm/@metamask/keyring-internal-api@4.0.3

View full report↗︎

@mathieuartu mathieuartu added Run Smoke E2E No QA Needed Apply this label when your PR does not need any QA effort. labels Mar 28, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Mar 28, 2025

https://bitrise.io/ Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 923000c
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/53c17739-06ff-4309-832f-c1fa8fc684d5

Note

  • You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Tip

  • Check the documentation if you have any doubts on how to understand the failure on bitrise

@github-actions
Copy link
Contributor

github-actions bot commented Mar 28, 2025

https://bitrise.io/ Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 01acd69
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/b6738606-ab7d-4503-8aec-f3b97bcf09a9

Note

  • You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Tip

  • Check the documentation if you have any doubts on how to understand the failure on bitrise

@mathieuartu mathieuartu changed the title chore: bump keyring-controller to ^21.0.1 chore: bump @metamask/keyring-controller to ^21.0.1 Mar 28, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Mar 28, 2025

https://bitrise.io/ Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 8edb5c1
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/ab05f755-26dc-48f6-a2fb-dec4beabd9d3

Note

  • You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

@mathieuartu mathieuartu marked this pull request as ready for review March 28, 2025 12:31
@mathieuartu mathieuartu requested a review from a team as a code owner March 28, 2025 12:31
@mathieuartu mathieuartu requested a review from a team March 28, 2025 12:31
@mathieuartu mathieuartu requested a review from a team as a code owner March 28, 2025 12:31
@tommasini
Copy link
Contributor

Heyy, I believe we do need to bump more packages that are dependent on the keyring controller version!
Example: accounts-controllers, assets-controllers, notifications-services-controller , preferences-controller, signature-controller,

OGPoyraz
OGPoyraz previously approved these changes Mar 28, 2025
Copy link
Member

@OGPoyraz OGPoyraz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confirmation changes LGTM

@mathieuartu mathieuartu marked this pull request as draft March 28, 2025 13:17
@mathieuartu mathieuartu changed the title chore: bump @metamask/keyring-controller to ^21.0.1 chore: bump controllers to core 343.0.0 [WIP] Mar 28, 2025
@mathieuartu mathieuartu changed the title chore: bump controllers to core 343.0.0 [WIP] chore: bump @metamask/keyring-controller to ^21.0.1 and align peer dependencies Mar 28, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Mar 28, 2025

https://bitrise.io/ Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 6a15fb2
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/e4127633-3246-4af6-91d6-6fb3fb9377ef

Note

  • You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

@mathieuartu mathieuartu marked this pull request as ready for review March 28, 2025 14:27
@mathieuartu mathieuartu requested review from a team as code owners March 28, 2025 14:27
@sonarqubecloud
Copy link

@mathieuartu mathieuartu changed the title chore: bump @metamask/keyring-controller to ^21.0.1 and align peer dependencies chore: bump controllers to Core v343 Mar 28, 2025
@mathieuartu mathieuartu changed the title chore: bump controllers to Core v343 chore: bump controllers to Core v343 [WIP] Mar 28, 2025
@mathieuartu mathieuartu requested review from a team as code owners March 28, 2025 15:27
networkClientId: NETWORK_CHAIN_ID.MAINNET,
type: RpcEndpointType.Custom,
name: 'Ethereum',
failoverUrls: [],
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks like a simple chainge with default value added to test, could be nice to know the usage of failoverUrls, its the first time i hear about them, also considering like it doesnt seem like its an optional value

Copy link
Contributor

@EtherWizard33 EtherWizard33 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

approved for wallet-ux file, looks like just a mock uipdate to unit test for the network select rpc selection

@sahar-fehri
Copy link
Contributor

Hey @mathieuartu , i had this PR to upgrade assets-controllers to v55.0.1 and handle to the introduced changes to detectNfts fct, do you think my PR can get in first?

@infiniteflower infiniteflower self-requested a review March 28, 2025 19:57
@mathieuartu mathieuartu closed this Apr 2, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Apr 2, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

No QA Needed Apply this label when your PR does not need any QA effort. team-identity-deprecated DEPRECATED: team no longer exists

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants