Repository navigation
Release/1377.0.0 - #11203
Merged
Merged
Release/1377.0.0#11203
Conversation
Contributor
Author
|
@metamaskbot update-changelogs |
This comment has been minimized.
This comment has been minimized.
Contributor
|
✅ No changelog changes needed. |
Prithpal-Sooriya
previously approved these changes
Oct 29, 2026
mcmire
reviewed
Oct 29, 2026
mcmire
left a comment
mcmire
left a comment
Collaborator
There was a problem hiding this comment.
One change needed but otherwise this looks good.
| "@metamask/subscription-controller": "^15.1.1", | ||
| "@metamask/transaction-controller": "^72.3.0", | ||
| "@metamask/subscription-controller": "^15.1.2", | ||
| "@metamask/transaction-controller": "^73.0.0", |
Collaborator
There was a problem hiding this comment.
Should we include this package in the release too?
Collaborator
There was a problem hiding this comment.
Ah I see that they are devDependencies. So sorry. This is fine then.
Contributor
Author
There was a problem hiding this comment.
In the end, @geositta akes me to bump perps to minor
mcmire
reviewed
Oct 29, 2026
mcmire
approved these changes
Oct 29, 2026
mcmire
left a comment
mcmire
left a comment
Collaborator
There was a problem hiding this comment.
Okay you should be good to merge this now 👍🏻
Kriys94
disabled auto-merge
October 29, 2026 21:09
Kriys94
enabled auto-merge
October 29, 2026 21:09
Merged
1 of 4 tasks
Naz-Ovh
pushed a commit
to 0x-fork/metamask-core
that referenced
this pull request
Nov 4, 2026
## Explanation Scoped release so clients can pick up MetaMask#11158 and MetaMask#11099. Monorepo release **1378.0.0** because [Release/1377.0.0](MetaMask#11203) is already open. - **`@metamask/kyc-controller` 0.13.0 → 0.14.0** (minor). Both changes are additive, so they stay in one minor. - `KycService.getDataShares` and `KycController.getDataShares` list the vendors a customer's verified identity data has been shared with (MetaMask#11158). Both are messenger actions. No new controller state, and no change to existing methods. - `KycController.ensureLocalUserSecret` creates and stores the UKYC `local_user_secret` when one does not already exist (MetaMask#11099). `startSession` still creates the secret when this method has not been called. The secret is not returned. No workspace package depends on `kyc-controller`, so nothing else is published. Other packages with unreleased changes are deferred. ## References - Ships MetaMask#11158 - Ships MetaMask#11099 - Unblocks MetaMask/metamask-mobile#38381 ## 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 communicated my changes to consumers by [updating changelogs for packages I've changed](https://github.com/MetaMask/core/tree/main/docs/processes/updating-changelogs.md) - [ ] I've introduced [breaking changes](https://github.com/MetaMask/core/tree/main/docs/processes/breaking-changes.md) in this PR and have prepared draft pull requests for clients and consumer packages to resolve them <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > The diff is version and changelog metadata only; functional changes were merged in earlier PRs and are not modified here. > > **Overview** > This is a **scoped release PR** that bumps the monorepo to **1378.0.0** and publishes **`@metamask/kyc-controller` 0.13.0 → 0.14.0**, with the package changelog cut from `[Unreleased]` into **`[0.14.0]`** (compare links updated accordingly). No application source files change in this diff—only `package.json` versions and `CHANGELOG.md`. > > The **0.14.0** notes document additive KYC work clients can pick up after publish, including **`getDataShares`** on the service and controller (messenger actions, no new persisted state), **`ensureLocalUserSecret`** to create/store the UKYC `local_user_secret` before session start when desired, optional **`currentStep`** on session status (plus related **`finalStatus`** mapping when step is `kyc`), and the associated exports/types called out in the changelog. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit b880f85. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY --> --------- Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: jiexi <jiexiluan@gmail.com>
Naz-Ovh
pushed a commit
to 0x-fork/metamask-core
that referenced
this pull request
Nov 4, 2026
## Explanation Reverts MetaMask#11205 (`Release 1378.0.0`), which was merged before its predecessor [Release/1377.0.0](MetaMask#11203) had been released. The release numbering assumed 1377 would land first, so this release has to come off `main`. The revert restores: - Root version `1378.0.0` → `1376.0.0` - `@metamask/kyc-controller` `0.14.0` → `0.13.0` - The `ensureLocalUserSecret` (MetaMask#11099), `getDataShares` (MetaMask#11158) and `currentStep` (MetaMask#11094) entries move back under `[Unreleased]` Nothing was published. The `main` run for the merge failed on an unrelated `rate-limit-controller` test, so the `Publish release` job was skipped. No tags were created, and npm still lists `@metamask/kyc-controller` at `0.13.0`. ## References - Reverts MetaMask#11205 ## 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 communicated my changes to consumers by [updating changelogs for packages I've changed](https://github.com/MetaMask/core/tree/main/docs/processes/updating-changelogs.md) - [ ] I've introduced [breaking changes](https://github.com/MetaMask/core/tree/main/docs/processes/breaking-changes.md) in this PR and have prepared draft pull requests for clients and consumer packages to resolve them Made with [Cursor](https://cursor.com) <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > Version and changelog-only revert with no code changes; aligns `main` with unpublished release state. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 9311ab8. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Naz-Ovh
pushed a commit
to 0x-fork/metamask-core
that referenced
this pull request
Nov 4, 2026
## Explanation Release **1378.0.0**. This PR bumps `@metamask/social-controllers` from `3.14.1` to `3.14.2` (patch) to ship [MetaMask#11209](MetaMask#11209), which passes the realtime feed item's `authorComment` through from the backend instead of deriving it from trade comments. The root monorepo version is bumped to `1378.0.0`, as the release check requires. `1378.0.0` is the next number after `1377.0.0` ([MetaMask#11203](MetaMask#11203)). An earlier `1378.0.0` attempt ([MetaMask#11205](MetaMask#11205)) was reverted in [MetaMask#11207](MetaMask#11207) before anything was published, so there is no `1378.0.0` tag. Packages deliberately left out of this release: - `@metamask/base-controller`, `@metamask/base-data-service`, `@metamask/controller-utils`, `@metamask/messenger`, and `@metamask/profile-sync-controller` are marked `intentionally-skip` in the release spec. `social-controllers` depends on them, but their unreleased changes are test, tooling, and dev-dependency changes with no consumer-facing API or behavior change. - Other packages with unreleased changes on `main` (for example `@metamask/kyc-controller`) are not part of this release. ## References - Ships [MetaMask#11209](MetaMask#11209) - Previous release: [MetaMask#11203](MetaMask#11203) - Reverted attempt: [MetaMask#11205](MetaMask#11205), [MetaMask#11207](MetaMask#11207) ## Checklist - [ ] I've updated the test suite for new or updated code as appropriate (N/A: version bump and changelog only) - [ ] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate (N/A) - [x] I've communicated my changes to consumers by [updating changelogs for packages I've changed](https://github.com/MetaMask/core/tree/main/docs/processes/updating-changelogs.md) - [ ] I've introduced [breaking changes](https://github.com/MetaMask/core/tree/main/docs/processes/breaking-changes.md) in this PR and have prepared draft pull requests for clients and consumer packages to resolve them (N/A: no breaking changes) <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > Version and changelog updates only; consumer-facing behavior was introduced in the earlier MetaMask#11209 merge, not in this diff. > > **Overview** > **Release-only PR** that bumps the monorepo to **`1378.0.0`** and publishes **`@metamask/social-controllers` `3.14.2`**, with no source changes in the diff. > > The **`3.14.2`** changelog records the patch already merged in [MetaMask#11209](MetaMask#11209): realtime feed items now use the backend’s **`authorComment`** (missing stays missing, **`null`** stays **`null`**, present values use the same validation as the REST feed, invalid values drop the item) instead of deriving it from trade comments. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 20e085a. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY --> Co-authored-by: Cursor <cursoragent@cursor.com>
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
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
Release 1377.0.0. This PR only bumps versions, finalizes changelogs, updates dependency ranges, and refreshes
yarn.lock. The behavior shipped here is already onmain.Three packages are major releases because their unreleased changelogs include breaking changes:
@metamask/transaction-controller72.3.0→73.0.0. Simulation now goes throughSentinelApiService:simulateTransactions. Consumers must construct aSentinelApiServiceand delegate that action.getSimulationConfignow returns{ newUrl?: string }only (#9476).@metamask/core-backend12.3.0→13.0.0.OHLCV_SERVICE_ALLOWED_ACTIONSno longer includesBackendWebSocketService:getConnectionInfoorBackendWebSocketService:findSubscriptionsByChannelPrefix(#10884). This release also addsfetchV5MultiAccountTransactions(#11194),LaunchpadTokenDetailsService, andChannelSubscriptionManager(#10884).@metamask/wallet20.0.0→21.0.0. Default initialization now includesNetworkEnablementController, and the wallet messenger delegatesSentinelApiService:simulateTransactions. Clients must registerMultichainNetworkController:getStateandSentinelApiService:simulateTransactionson the wallet messenger (#10997, #9476).These packages are included so they can depend on
transaction-controller^73.0.0and, where they use it,core-backend^13.0.0:@metamask/assets-controller20.1.0@metamask/assets-controllers113.0.1@metamask/bridge-controller83.1.3@metamask/bridge-status-controller78.0.1@metamask/client-utils3.1.0@metamask/eip-5792-middleware4.1.0@metamask/gator-permissions-controller6.1.0@metamask/money-account-utils2.2.0@metamask/network-enablement-controller7.1.0@metamask/phishing-controller18.3.0@metamask/profile-metrics-controller5.2.1@metamask/shield-controller7.1.1@metamask/smart-transactions-controller27.2.1@metamask/social-controllers3.14.1@metamask/subscription-controller15.1.2@metamask/transaction-pay-controller30.3.2@metamask/transaction-pay-middleware2.0.1@metamask/user-operation-controller42.1.0Notable changes besides the dependency bumps:
@metamask/assets-controller: optionalpricePercentChange5mandpricePercentChange4honFungibleAssetPrice(#11201).@metamask/client-utils:predictionSettledonActivityKind(#11169), plus fee fixes for contract-interaction fallback and OP Stack L1/operator fees (#11013, #9630).@metamask/network-enablement-controller: preserve enablement when a config-registry network is auto-enabled (#10763).@metamask/phishing-controller: Arc (0x13b2) token scanning (#11144).@metamask/transaction-pay-controller: shared recipient resolution and Hyperliquid perps deposit detection (#10887, #11026).@metamask/earn-controller,@metamask/money-account-mfa-whitelist,@metamask/money-account-upgrade-controller,@metamask/network-connection-banner-controller,@metamask/perps-controller, and@metamask/signature-controlleronly have dependency ranges updated. They are not version-bumped and are not published in this release.References
Checklist
Note
Medium Risk
The diff is low-risk mechanically, but the published majors force client upgrades around transaction simulation, backend WebSocket actions, and wallet messenger registration—areas that affect core wallet behavior.
Overview
This PR cuts release 1377.0.0 by bumping the root monorepo version, publishing new semver tags for many
@metamask/*packages, moving unreleased changelog entries into versioned sections, updating inter-package dependency ranges, and refreshingyarn.lock. There is no new application logic in the diff—only release bookkeeping for work already onmain.The release centers on three major packages whose changelogs document breaking changes:
@metamask/transaction-controller73.0.0(simulation viaSentinelApiService:simulateTransactions;getSimulationConfigshape change),@metamask/core-backend13.0.0(WebSocket allowed-actions cleanup plus new backend APIs/services), and@metamask/wallet21.0.0(defaultNetworkEnablementControllerwiring and Sentinel simulation delegation on the wallet messenger). Dozens of other packages are minor/patch bumped mainly to depend ontransaction-controller^73.0.0and, where applicable,core-backend^13.0.0.Several workspaces only have
package.jsondependency range updates (e.g.earn-controller,money-account-upgrade-controller,signature-controller) without a version bump in this PR. A few packages also document feature fixes in their new changelog sections (e.g.assets-controllerprice change fields,client-utilsactivity kinds/fees,phishing-controllerArc scanning) as part of the versions being published here.Reviewed by Cursor Bugbot for commit 5a253e4. Bugbot is set up for automated code reviews on this repo. Configure here.