Repository navigation
Tags: MetaMask/core
Tags
Release/1325.0.0 (#10777) ## Explanation This is a new release for `@metamask/kyc-controller`. - Monorepo version `1324.0.0` → `1325.0.0` - `@metamask/kyc-controller` `0.7.0` → `0.8.0` `0.8.0` publishes the changes already on `main`: - Export `KYC_STATUSES` and `TERMINAL_SESSION_STATUSES` ([#10771](#10771)) - Bump `@metamask/profile-sync-controller` from `^34.0.2` to `^34.0.3` ([#10761](#10761)) - `KycController.hasCompletedSessionDisclaimers` no longer throws 409 if called when session is in terminal state ## References * #10771 * #10761 * #10760 ## 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 ## Test plan - [ ] Confirm the changelog `0.8.0` section matches the consumer-facing changes since `0.7.0` - [ ] Confirm only `@metamask/kyc-controller` and the monorepo version are bumped - [ ] After merge, confirm npm publish of `@metamask/kyc-controller@0.8.0` once `npm-publishers` approves Made with [Cursor](https://cursor.com) --------- Co-authored-by: Cursor <cursoragent@cursor.com>
Release/1324.0.0 (#10774) ## Explanation This is a new release for `social-controllers` package. ## 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 --> ## 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 - [ ] 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** > Version and changelog-only release cut; behavioral changes were already merged in referenced PRs. > > **Overview** > Cuts **monorepo release `1324.0.0`** by publishing **`@metamask/social-controllers@3.7.0`**: bumps root and package `version` fields and promotes the existing `[Unreleased]` changelog into a **`[3.7.0]`** section with updated compare links. > > The **3.7.0** notes document shipped capabilities from prior merges: new follow APIs (`fetchMyFollowers`, `fetchMyFollowing`, `fetchTraderFollowing`, optional `mutuals` on `fetchFollowers`), looser `Position`/feed validation and per-item feed drops on validation failure, trending realtime feed subscription in `SocialRealtimeService`, and a `@metamask/profile-sync-controller` dependency bump. **This PR does not change source**—only release metadata. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit cbaed50. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Release 1323.0.0 (#10772) Minor release of `@metamask/transaction-controller`. <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Medium Risk** > Propagates a minor transaction-controller release that changes re-simulation and L1 gas estimation on some chains; the diff is mostly version bumps but downstream apps inherit tx-path behavior changes. > > **Overview** > **Monorepo release 1323.0.0** cuts **`@metamask/transaction-controller@72.2.0`** and updates every dependent workspace package (assets, bridge, wallet, EIP-5792 middleware, etc.) from `^72.1.0` to `^72.2.0`, with matching **Unreleased** changelog entries and **`yarn.lock`** resolution. > > Consumers of this release pick up **transaction-controller 72.2.0** behavior: an optional **`isTransactionTrusted`** callback on `TransactionControllerOptions` so future-block re-simulation runs only for transactions the host marks untrusted, **Ink Mainnet / Ink Sepolia** treated as OP Stack for L1 gas estimates, plus minor dependency bumps inside that package (`nonce-tracker`, `ethereum-cryptography`, etc.). This PR does not add new application logic beyond versioning and dependency wiring. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 86d0826. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Release/1322.0.0 (#10767) ## Explanation Monorepo release **1322.0.0**. Publishes `@metamask/ramps-controller@27.0.1` with the Active MoonPay customer check from #10766, plus the already-landed `@metamask/profile-sync-controller` bump to `^34.0.3` that was still unreleased. `@metamask/transaction-pay-controller` is the only workspace package that depends on ramps. Yarn constraints require that dependency range to be `^` plus the current ramps version, so this release also publishes `@metamask/transaction-pay-controller@30.0.3` with that range bump. Nothing else in the monorepo depends on transaction-pay, so the bump stops there. This matches release 1320.0.0, which published a transaction-pay patch when ramps moved to 27.0.0. ## References * #10766 ## 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) --------- Co-authored-by: Cursor <cursoragent@cursor.com>
Release/1322.0.0 (#10767) ## Explanation Monorepo release **1322.0.0**. Publishes `@metamask/ramps-controller@27.0.1` with the Active MoonPay customer check from #10766, plus the already-landed `@metamask/profile-sync-controller` bump to `^34.0.3` that was still unreleased. `@metamask/transaction-pay-controller` is the only workspace package that depends on ramps. Yarn constraints require that dependency range to be `^` plus the current ramps version, so this release also publishes `@metamask/transaction-pay-controller@30.0.3` with that range bump. Nothing else in the monorepo depends on transaction-pay, so the bump stops there. This matches release 1320.0.0, which published a transaction-pay patch when ramps moved to 27.0.0. ## References * #10766 ## 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) --------- Co-authored-by: Cursor <cursoragent@cursor.com>
Release 1323.0.0 (#10772) Minor release of `@metamask/transaction-controller`. <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Medium Risk** > Propagates a minor transaction-controller release that changes re-simulation and L1 gas estimation on some chains; the diff is mostly version bumps but downstream apps inherit tx-path behavior changes. > > **Overview** > **Monorepo release 1323.0.0** cuts **`@metamask/transaction-controller@72.2.0`** and updates every dependent workspace package (assets, bridge, wallet, EIP-5792 middleware, etc.) from `^72.1.0` to `^72.2.0`, with matching **Unreleased** changelog entries and **`yarn.lock`** resolution. > > Consumers of this release pick up **transaction-controller 72.2.0** behavior: an optional **`isTransactionTrusted`** callback on `TransactionControllerOptions` so future-block re-simulation runs only for transactions the host marks untrusted, **Ink Mainnet / Ink Sepolia** treated as OP Stack for L1 gas estimates, plus minor dependency bumps inside that package (`nonce-tracker`, `ethereum-cryptography`, etc.). This PR does not add new application logic beyond versioning and dependency wiring. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 86d0826. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Release/1324.0.0 (#10774) ## Explanation This is a new release for `social-controllers` package. ## 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 --> ## 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 - [ ] 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** > Version and changelog-only release cut; behavioral changes were already merged in referenced PRs. > > **Overview** > Cuts **monorepo release `1324.0.0`** by publishing **`@metamask/social-controllers@3.7.0`**: bumps root and package `version` fields and promotes the existing `[Unreleased]` changelog into a **`[3.7.0]`** section with updated compare links. > > The **3.7.0** notes document shipped capabilities from prior merges: new follow APIs (`fetchMyFollowers`, `fetchMyFollowing`, `fetchTraderFollowing`, optional `mutuals` on `fetchFollowers`), looser `Position`/feed validation and per-item feed drops on validation failure, trending realtime feed subscription in `SocialRealtimeService`, and a `@metamask/profile-sync-controller` dependency bump. **This PR does not change source**—only release metadata. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit cbaed50. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Release/1322.0.0 (#10767) ## Explanation Monorepo release **1322.0.0**. Publishes `@metamask/ramps-controller@27.0.1` with the Active MoonPay customer check from #10766, plus the already-landed `@metamask/profile-sync-controller` bump to `^34.0.3` that was still unreleased. `@metamask/transaction-pay-controller` is the only workspace package that depends on ramps. Yarn constraints require that dependency range to be `^` plus the current ramps version, so this release also publishes `@metamask/transaction-pay-controller@30.0.3` with that range bump. Nothing else in the monorepo depends on transaction-pay, so the bump stops there. This matches release 1320.0.0, which published a transaction-pay patch when ramps moved to 27.0.0. ## References * #10766 ## 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) --------- Co-authored-by: Cursor <cursoragent@cursor.com>
Release/1325.0.0 (#10777) ## Explanation This is a new release for `@metamask/kyc-controller`. - Monorepo version `1324.0.0` → `1325.0.0` - `@metamask/kyc-controller` `0.7.0` → `0.8.0` `0.8.0` publishes the changes already on `main`: - Export `KYC_STATUSES` and `TERMINAL_SESSION_STATUSES` ([#10771](#10771)) - Bump `@metamask/profile-sync-controller` from `^34.0.2` to `^34.0.3` ([#10761](#10761)) - `KycController.hasCompletedSessionDisclaimers` no longer throws 409 if called when session is in terminal state ## References * #10771 * #10761 * #10760 ## 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 ## Test plan - [ ] Confirm the changelog `0.8.0` section matches the consumer-facing changes since `0.7.0` - [ ] Confirm only `@metamask/kyc-controller` and the monorepo version are bumped - [ ] After merge, confirm npm publish of `@metamask/kyc-controller@0.8.0` once `npm-publishers` approves Made with [Cursor](https://cursor.com) --------- Co-authored-by: Cursor <cursoragent@cursor.com>
Release/1321.0.0 (#10761) ## 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? --> ## 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 --> ## 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** > Patch-level dependency propagation with a narrow AES-GCM Web Crypto compatibility fix; no breaking API or logic changes in this PR’s diff. > > **Overview** > **Monorepo release 1321.0.0** that publishes **`@metamask/cryptography@1.1.2`** and rolls that fix through **`@metamask/profile-sync-controller@34.0.3`** and every package that depends on profile sync. > > The substantive change being released is in **cryptography**: AES-GCM **`encrypt`/`decrypt` no longer pass `additionalData: undefined` into Web Crypto**, which Chrome rejects ([#10757](#10757)). Profile sync bumps its **`@metamask/cryptography`** range to **`^1.1.2`** ([#10761](#10761)); changelogs and **`package.json`** across account-tree, assets, bridge, claims, core-backend, kyc, notifications, profile*, ramps, shield, smart-transactions, social, subscription, and related workspaces now require **`@metamask/profile-sync-controller@^34.0.3`**. **`yarn.lock`** is updated to match. > > There are **no new controller or service code changes** in this diff—only version bumps, changelog entries, and lockfile updates. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 003c8a8. 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: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
PreviousNext