Release/1280.0.0 - #10409
Merged
Merged
Release/1280.0.0#10409
Conversation
…2.3.0 The `create-release-branch` tool auto-populated `[32.3.0]` with several `chore(deps)` renovate bumps of dev dependencies. Per the release guidelines these are not consumer-facing, so remove them. Co-authored-by: Cursor <cursoragent@cursor.com>
Member
Author
|
@metamaskbot update-changelogs |
This comment has been minimized.
This comment has been minimized.
Contributor
|
❌ Failed to push changelog fixes. Check the workflow run for details. |
mathieuartu
approved these changes
Sep 23, 2026
cryptodev-2s
approved these changes
Sep 23, 2026
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Explanation
Publish
@metamask/profile-sync-controller@32.3.0so clients can consume the additive changes that have accumulated onmainsince 32.2.0, including thepairedIdentifierIdsfield onUserProfileinsrpSessionData(#10394).Minor bump: the release only adds new, optional API surface (AAL2-gated MFA enrollment, elevated tokens for credential enrollment,
pairedIdentifierIds) and bumps the internalimmerdependency. Nothing existing changes, so it is not breaking.All 15 workspace packages that depend on
@metamask/profile-sync-controllernow pin^32.3.0; none are being published in this release.yarn.lockis updated accordingly.References
pairedIdentifierIdstoUserProfile: feat(authentication-controller): AddpairedIdentifierIdstoUserProfileinsrpSessionData#10394immerfrom^9.0.6to^9.0.21: fix(deps): update dependency immer to ^9.0.21 #10331Checklist
Note
Medium Risk
Releases auth/MFA and profile-session API surface; the diff is dependency pins only, but consumers will pick up security-sensitive behavior from 32.3.0.
Overview
This release PR cuts
@metamask/profile-sync-controller@32.3.0(monorepo1280.0.0) and propagates it across the workspace. The 15 packages that depend on profile sync now pin^32.3.0inpackage.json, with matching Unreleased changelog notes andyarn.lockupdates; those dependents are not republished here.The 32.3.0 changelog section documents what clients get from this publish: AAL2-gated MFA enrollment (elevated
accessTokenforbeginMfaEnrollment, new MFA error codes /StepUpRequiredError,retry_after_secondshandling),pairedIdentifierIdsonUserProfileinsrpSessionData, and an internalimmerbump. No runtime code changes appear in this diff—only versioning and release notes.Reviewed by Cursor Bugbot for commit 3a7ced6. Bugbot is set up for automated code reviews on this repo. Configure here.