chore: bump @metamask/{keyring, profile-sync}-controller#30637
Merged
mikesposito merged 22 commits intomainfrom Mar 7, 2025
Merged
chore: bump @metamask/{keyring, profile-sync}-controller#30637mikesposito merged 22 commits intomainfrom
@metamask/{keyring, profile-sync}-controller#30637mikesposito merged 22 commits intomainfrom
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
|
New and updated dependencies detected. Learn more about Socket for GitHub ↗︎
|
|
👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎ This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. |
Collaborator
|
Policies updated. 🧠 Learn how: https://lavamoat.github.io/guides/policy-diff/#what-to-look-for-when-reviewing-a-policy-diff |
4c87f28 to
c4a8c9d
Compare
Member
Author
|
@metamaskbot update-policies |
Collaborator
|
Policies updated. 🧠 Learn how: https://lavamoat.github.io/guides/policy-diff/#what-to-look-for-when-reviewing-a-policy-diff |
4 tasks
@metamask/keyring-controller@metamask/{keyring, profile-sync}-controller
Member
Author
|
mikesposito
added a commit
to MetaMask/core
that referenced
this pull request
Mar 3, 2025
## Explanation <!-- Thanks for your contribution! Take a moment to answer these questions so that reviewers have the information they need to properly understand your changes: * What is the current state of things and why does it need to change? * What is the solution your changes offer and how does it work? * Are there any changes whose purpose might not obvious to those unfamiliar with the domain? * If your primary goal was to update one package but you found you had to update another one along the way, why did you do so? * If you had to upgrade a dependency, why did you do so? --> This PR bumps these packages across the core controllers: - `@metamask/eth-simple-keyring` - `@metamask/eth-hd-keyring` - `@metamask/keyring-internal-api` The package is being updated on Extension by this PR: MetaMask/metamask-extension#30637 ## References <!-- Are there any issues that this pull request is tied to? Are there other links that reviewers should consult to understand these changes better? Are there client or consumer pull requests to adopt any breaking changes? For example: * Fixes #12345 * Related to #67890 --> ## Changelog <!-- If you're making any consumer-facing changes, list those changes here as if you were updating a changelog, using the template below as a guide. (CATEGORY is one of BREAKING, ADDED, CHANGED, DEPRECATED, REMOVED, or FIXED. For security-related issues, follow the Security Advisory process.) Please take care to name the exact pieces of the API you've added or changed (e.g. types, interfaces, functions, or methods). If there are any breaking changes, make sure to offer a solution for consumers to follow once they upgrade to the changes. Finally, if you're only making changes to development scripts or tests, you may replace the template below with "None". --> ### `@metamask/keyring-controller` - **CHANGED**: Bump `@metamask/eth-simple-keyring` from `^8.1.0` to `^9.0.0` ([#5405](#5405)) - **CHANGED**: Bump `@metamask/eth-hd-keyring` from `^10.0.0` to `^11.0.0` ([#5405](#5405)) - **CHANGED**: Bump `@metamask/keyring-internal-api` from `^4.0.3` to `^5.0.0` ([#5405](#5405)) ### `@metamask/accounts-controller` - **CHANGED**: Bump `@metamask/keyring-internal-api` from `^4.0.3` to `^5.0.0` ([#5405](#5405)) ### `@metamask/profile-sync-controller` - **CHANGED**: Bump `@metamask/keyring-internal-api` from `^4.0.3` to `^5.0.0` ([#5405](#5405)) ### `@metamask/assets-controller` - **CHANGED**: Bump `@metamask/keyring-internal-api` from `^4.0.3` to `^5.0.0` ([#5405](#5405)) ### `@metamask/multichain-transaction-controller` - **CHANGED**: Bump `@metamask/keyring-internal-api` from `^4.0.3` to `^5.0.0` ([#5405](#5405)) ## Checklist - [ ] I've updated the test suite for new or updated code as appropriate - [ ] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate - [ ] I've highlighted breaking changes using the "BREAKING" category above as appropriate - [ ] I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes
4 tasks
This was
linked to
issues
Mar 4, 2025
Member
Author
|
@metamaskbot update-policies |
Collaborator
Builds ready [3aad368]
Page Load Metrics (1543 ± 44 ms)
Bundle size diffs [🚀 Bundle size reduced!]
|
mathieuartu
approved these changes
Mar 5, 2025
mathieuartu
added a commit
to MetaMask/core
that referenced
this pull request
Mar 5, 2025
## Explanation This PR makes the necessary changes so that `UserStorageController` and `AuthenticationController` consumes the profile sync SDK. That means that there's no longer controller specific logic nor services related to authentication and user storage. Test coverages has also been increased to almost 100% for all things related to authentication and user storage, for controller & SDK. ## References Related to: https://consensyssoftware.atlassian.net/browse/IDENTITY-48 Extension test drive PR: MetaMask/metamask-extension#30681 Note that when bumping the version on the extension and mobile, some changes will be mandatory: - Updating the mock storage key for both identity and notifications E2E tests constants - Updating `sessionData` shapes everywhere - Add a migration to manage `sessionData` shape changes so that it is reset for users still using the previous shape - Bumping `KeyringController` to `^19.2.1` if not done already, and take care of the breaking changes this version adds on extension - This will most likely be fixed with MetaMask/metamask-extension#30637 ## Changelog <!-- If you're making any consumer-facing changes, list those changes here as if you were updating a changelog, using the template below as a guide. (CATEGORY is one of BREAKING, ADDED, CHANGED, DEPRECATED, REMOVED, or FIXED. For security-related issues, follow the Security Advisory process.) Please take care to name the exact pieces of the API you've added or changed (e.g. types, interfaces, functions, or methods). If there are any breaking changes, make sure to offer a solution for consumers to follow once they upgrade to the changes. Finally, if you're only making changes to development scripts or tests, you may replace the template below with "None". --> ### `@metamask/profile-sync-controller` - **CHANGED**: `UserStorageController` and `AuthenticationController` now use the SDK under the hood. - **CHANGED**(**BREAKING**): `AuthenticationController` state entry `sessionData` has changed shape to fully reflect the `LoginResponse` SDK type. - **CHANGED**(**BREAKING**): `UserStorageController` cannot use the `'AuthenticationController:performSignOut'` action anymore. ### `@metamask/notification-services-controller` - **CHANGED**: Change import for mock access token (only related to tests) ## 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
Contributor
|
LGTM! |
matthewwalsh0
approved these changes
Mar 6, 2025
Collaborator
Builds ready [ea84681]
Page Load Metrics (1718 ± 56 ms)
Bundle size diffs [🚀 Bundle size reduced!]
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
These packages are being bumped to their latest version:
@metamask/keyring-controlleraddNewKeyringmethod now returnsPromise<KeyringMetadata>instead ofPromise<unknown>(#5372)KeyringMetadata.idto access the created keyring instance viawithKeyring.withKeyringmethod now requires a callback argument of type({ keyring: SelectedKeyring; metadata: KeyringMetadata }) => Promise<CallbackResult>(#5372)@metamask/keyring-internal-apifrom^4.0.3to^5.0.0(#5405)@metamask/eth-hd-keyringfrom^10.0.0to^11.0.0(#5405)@metamask/eth-simple-keyringfrom^8.1.0to^9.0.0(#5405)@metamask/profile-sync-controller@metamask/keyring-internal-apifrom^4.0.3to^5.0.0(#5405)@metamask/eth-ledger-bridge-keyringLedgerKeyringnow implements theKeyringtype (#194)EventEmitteranymore.LedgerKeyring.accountsclass variable is now areadonly Hex[]array.addAccountsmethod signature has been changed:amountnumber parameter is now required to specify the number of accounts to add.Hexaddresses.unlockmethod now returnsPromise<Hex>.getAccountsmethod now returnsPromise<Hex[]>.deserializemethod now requires aLedgerKeyringSerializedStatetyped parameter.signTransactionmethod now accepts anHextyped value as theaddressparameter.signMessagemethod now accepts anHextyped value as thewithAccountparameter.signPersonalMessagemethod now accepts anHextyped value as thewithAccountparameter.signTypedDatamethod now accepts anHextyped value as thewithAccountparameter.unlockAccountByAddressmethod now accepts anHextyped value as theaddressparameter.Related issues
Fixes:
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist