Bring all controller packages up to date with (at least) core release 125.0.0

[mcmire]

What is this about?

Release 125.0.0 of the core monorepo included new versions for all packages. We want to make sure that the extension is using at least these versions for the controllers it's using so that we know everything is using the latest version of base-controller, and also that all packages have a package.json with the correct types field.

Scenario

No response

Design

No response

Technical Details

Outdated packages:

• @metamask/accounts-controller ^11.0.0 -> ^12.0.1 (latest: ^13.0.0)
• @metamask/address-book-controller ^3.1.7 -> ^4.0.1
• @metamask/approval-controller ^6.0.0 -> ^6.0.1
• @metamask/assets-controllers ^26.0.0 (patched) -> ^27.0.1 (latest: ^28.0.0)
• @metamask/base-controller ^4.1.0 -> ^5.0.1
• @metamask/ens-controller ^9.0.0 -> ^10.0.1
• @metamask/eth-keyring-controller ^16.0.0 -> remove
• @metamask/gas-fee-controller ^14.0.0 -> ^14.0.1 (latest: ^15.0.0)
• @metamask/keyring-controller ^13.0.0 (patched) -> ^14.0.1 (latest: ^15.0.0)
• @metamask/logging-controller ^2.0.2 -> ^3.0.1
• @metamask/name-controller ^4.2.0 -> ^6.0.1
• @metamask/notification-controller ^3.0.0 -> ^5.0.1
• @metamask/permission-log-controller ^1.0.0 -> ^2.0.1
• @metamask/phishing-controller ^8.0.2 -> ^9.0.1
• @metamask/rate-limit-controller ^3.0.0 -> ^5.0.1
• @metamask/signature-controller ^12.0.0 -> ^14.0.1 (latest: ^15.0.0)
• @metamask/user-operation-controller ^6.0.0 -> ^6.0.1 (latest: ^8.0.0)

Here is the order of how we should address these:

• [x] @metamask/approval-controller
  • Addressed via https://github.com/MetaMask/metamask-extension/pull/24141
• [x] @metamask/keyring-controller
  • Addressed via https://github.com/MetaMask/metamask-extension/pull/24199
• [x] @metamask/logging-controller + @metamask/signature-controller (relies on: approval, keyring)
  • Addressed via https://github.com/MetaMask/metamask-extension/pull/24143
• [x] @metamask/accounts-controller (+ @metamask/snaps-controllers)
  • Addressed via https://github.com/MetaMask/metamask-extension/pull/24130
• [x] @metamask/gas-fee-controller
  • Addressed via https://github.com/MetaMask/metamask-extension/pull/23717
• [x] @metamask/address-book-controller
  • Addressed via https://github.com/MetaMask/metamask-extension/pull/24205
• [x] @metamask/ens-controller
  • Addressed via https://github.com/MetaMask/metamask-extension/pull/24207
• [x] @metamask/base-controller
  • Addressed via https://github.com/MetaMask/metamask-extension/pull/24209
• [x] @metamask/name-controller
  • Addressed via https://github.com/MetaMask/metamask-extension/pull/24229
• [x] @metamask/notification-controller
  • Addressed via https://github.com/MetaMask/metamask-extension/pull/24430
• [x] @metamask/permission-log-controller
  • Addressed via https://github.com/MetaMask/metamask-extension/pull/24432
• [x] @metamask/phishing-controller
  • Addressed via https://github.com/MetaMask/metamask-extension/pull/24311
• [x] @metamask/rate-limit-controller
  • Addressed via https://github.com/MetaMask/metamask-extension/pull/24433
• [x] @metamask/assets-controllers (relies on: accounts, approval, keyring, network)
  • Addressed via https://github.com/MetaMask/metamask-extension/pull/24360
• [x] @metamask/user-operation-controller (relies on: approval, gas-fee, keyring, network)
  • Addressed via https://github.com/MetaMask/metamask-extension/pull/24130

Threat Modeling Framework

No response

Acceptance Criteria

No response

Stakeholder review needed before the work gets merged

• [ ] Engineering (needed in most cases)
• [ ] Design
• [ ] Product
• [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
• [ ] Security
• [ ] Legal
• [ ] Marketing
• [ ] Management (please specify)
• [ ] Other (please specify)

References

No response

[mcmire]

This is finally done!