chore: bump @metamask/{preferences,assets}-controllers

[cryptodev-2s]

Description

This PR bumps:

• @metamask/preferences-controller to 15.0.1
• @metamask/assets-controllers to 45.1.1

Related issues

Fixes: #12382, #12380

Manual testing steps

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

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.

[github-actions]

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.

[github-actions]

Bitrise

🔄🔄🔄 pr_smoke_e2e_pipeline started on Bitrise...🔄🔄🔄

Commit hash: 94b67d0
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/be78ec4f-7815-456f-93ee-8331a9e09077

Note

• This comment will auto-update when build completes
• 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

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@metamask/[email protected]	None	+2	2.38 MB	metamaskbot
npm/@metamask/[email protected]	None	0	105 kB	metamaskbot
npm/@metamask/[email protected]	None	0	140 kB	metamaskbot

🚮 Removed packages: npm/@metamask/[email protected], npm/@metamask/[email protected], npm/@metamask/[email protected]

View full report↗︎

[tommasini]

Actually, should we merge keyring controller to v19 first?

metamask-mobile/package.json

Line 169 in 93c3823

"@metamask/keyring-controller": "^18.0.0",

changelog: https://github.com/MetaMask/core/blob/%40metamask/preferences-controller%4015.0.1/packages/preferences-controller/CHANGELOG.md

It seems almost ready: #12555

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 3f54694
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/b539bb36-bd06-46ad-82e2-0987d5b9c70c

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

[cryptodev-2s]

Actually, should we merge keyring controller to v19 first?

metamask-mobile/package.json

Line 169 in 93c3823

"@metamask/keyring-controller": "^18.0.0",

changelog: https://github.com/MetaMask/core/blob/%40metamask/preferences-controller%4015.0.1/packages/preferences-controller/CHANGELOG.md

It seems almost ready: #12555

@tommasini We are using @metamask/keyring-controller within @metamask/preferences-controller at this location: https://github.com/MetaMask/core/blob/main/packages/preferences-controller/src/PreferencesController.ts#L272. In this context, we only listen to keyring state changes. Reviewing the CHANGELOG for @metamask/keyring-controller from version 18 to 19, there are no state changes or updates that would affect this version bump.

But I have no problem waiting for the other one to be merged first.

[Gudahtt]

The keyring controller update is now merged, so perhaps we can update this branch to resolve the peer dependency warning before merging

[Gudahtt]

Could you bump the assets-controllers package to v45 as well? That would resolve the last peer dependency warning introduced by this change (and it would resolve two existing peer dependency warnings). There are no breaking changes in that bump except these peer dependency changes.

[github-actions]

Bitrise

🔄🔄🔄 pr_smoke_e2e_pipeline started on Bitrise...🔄🔄🔄

Commit hash: d2d1b22
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/8ee1b5ee-e1e1-4556-9f15-6d60e8e5656c

Note

• This comment will auto-update when build completes
• 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

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 896a2e6
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/a54916bf-c4cb-4e1d-8d02-18f42f26be81

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

[Gudahtt]

LGTM!

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud