Repository navigation
Release/1378.0.0 - #11210
Merged
Merged
Release/1378.0.0#11210
Conversation
Root monorepo version 1378.0.0. Patch release that includes #11209 (realtime feed authorComment pass-through). Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
|
✅ No changelog changes needed. |
salimtb
approved these changes
Oct 30, 2026
zone-live
approved these changes
Oct 30, 2026
Closed
2 of 4 tasks
Naz-Ovh
pushed a commit
to 0x-fork/metamask-core
that referenced
this pull request
Nov 4, 2026
## Explanation Release **1380.0.0**. This PR bumps `@metamask/kyc-controller` from `0.13.0` to `0.14.0` (minor). The unreleased changelog adds public API: optional `currentStep` on `KycSessionStatus`, `KycController.ensureLocalUserSecret`, and `getDataShares` on both the service and the controller, plus their exported types. It also maps a session that reports `finalStatus: pending` with `currentStep: kyc` back to `finalStatus: new`, which restores the previous meaning of `pending` (only after SumSub is fully submitted). That behavior change is not marked breaking. The root monorepo version is bumped to `1380.0.0`. No other package in this repo depends on `@metamask/kyc-controller`, so no other packages are included. Dev-only commits since `0.13.0` (the `nock` bump and a test import change) are left out of the changelog. ## References - Ships [MetaMask#11094](MetaMask#11094), [MetaMask#11099](MetaMask#11099), and [MetaMask#11158](MetaMask#11158) - Previous merged release: [MetaMask#11210](MetaMask#11210) ## 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-only release with no new runtime changes in this PR; consumer impact comes from the already-merged kyc-controller APIs and status mapping described in the changelog. > > **Overview** > This PR cuts **release 1380.0.0** for the core monorepo by bumping the root version from `1379.0.0` to **1380.0.0** > > It publishes **`@metamask/kyc-controller` `0.14.0`**, moving the existing Unreleased changelog into a **`[0.14.0]`** section and updating compare links. There is **no application code in the diff**—only version and changelog housekeeping. > > The **0.14.0** notes document what consumers get from earlier merged work: optional **`currentStep`** on **`KycSessionStatus`**, **`ensureLocalUserSecret`**, **`getDataShares`** on the service and controller, related exports, and a **behavior tweak** that maps API **`pending` + `currentStep: kyc`** back to **`finalStatus: new`** so partially submitted flows are not treated like post–SumSub pending. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 1727a26. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY --> Signed-off-by: Sébastien Van Eyck <sebastien.vaneyck@consensys.net>
This branch was successfully deployed
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 1378.0.0. This PR bumps
@metamask/social-controllersfrom3.14.1to3.14.2(patch) to ship #11209, which passes the realtime feed item'sauthorCommentthrough from the backend instead of deriving it from trade comments. The root monorepo version is bumped to1378.0.0, as the release check requires.1378.0.0is the next number after1377.0.0(#11203). An earlier1378.0.0attempt (#11205) was reverted in #11207 before anything was published, so there is no1378.0.0tag.Packages deliberately left out of this release:
@metamask/base-controller,@metamask/base-data-service,@metamask/controller-utils,@metamask/messenger, and@metamask/profile-sync-controllerare markedintentionally-skipin the release spec.social-controllersdepends on them, but their unreleased changes are test, tooling, and dev-dependency changes with no consumer-facing API or behavior change.main(for example@metamask/kyc-controller) are not part of this release.References
Checklist
Note
Low Risk
Version and changelog updates only; consumer-facing behavior was introduced in the earlier #11209 merge, not in this diff.
Overview
Release-only PR that bumps the monorepo to
1378.0.0and publishes@metamask/social-controllers3.14.2, with no source changes in the diff.The
3.14.2changelog records the patch already merged in #11209: realtime feed items now use the backend’sauthorComment(missing stays missing,nullstaysnull, present values use the same validation as the REST feed, invalid values drop the item) instead of deriving it from trade comments.Reviewed by Cursor Bugbot for commit 20e085a. Bugbot is set up for automated code reviews on this repo. Configure here.