Tags: MetaMask/core
Tags
Release/929.0.0 (#8540) <!-- CURSOR_SUMMARY --> > [!NOTE] > **Low Risk** > Release metadata/changelog-only changes with no runtime code modifications; main risk is versioning/release coordination (e.g., consumers picking up the new major version). > > **Overview** > Updates the monorepo version from `928.0.0` to `929.0.0`. > > Publishes `@metamask/authenticated-user-storage` as `1.0.0` (from `0.0.0`) and finalizes its `CHANGELOG.md` by adding a `1.0.0` section, noting a breaking rename, and updating compare/release links. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 100ab70. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Release/928.0.0 (#8529) ## Explanation This PR releases v1.0.0 of the money account upgrade controller <!-- 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 - [ ] 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 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** > Release-only changes: version bumps and changelog link updates with no runtime logic modifications. > > **Overview** > **Cuts a new release** by bumping the monorepo version to `928.0.0`. > > Publishes `@metamask/money-account-upgrade-controller` as `1.0.0` (from `0.0.0`) and finalizes its changelog with a `1.0.0` section and updated compare/release links. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 3d3be81. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Release/928.0.0 (#8529) ## Explanation This PR releases v1.0.0 of the money account upgrade controller <!-- 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 - [ ] 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 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** > Release-only changes: version bumps and changelog link updates with no runtime logic modifications. > > **Overview** > **Cuts a new release** by bumping the monorepo version to `928.0.0`. > > Publishes `@metamask/money-account-upgrade-controller` as `1.0.0` (from `0.0.0`) and finalizes its changelog with a `1.0.0` section and updated compare/release links. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 3d3be81. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Release/929.0.0 (#8540) <!-- CURSOR_SUMMARY --> > [!NOTE] > **Low Risk** > Release metadata/changelog-only changes with no runtime code modifications; main risk is versioning/release coordination (e.g., consumers picking up the new major version). > > **Overview** > Updates the monorepo version from `928.0.0` to `929.0.0`. > > Publishes `@metamask/authenticated-user-storage` as `1.0.0` (from `0.0.0`) and finalizes its `CHANGELOG.md` by adding a `1.0.0` section, noting a breaking rename, and updating compare/release links. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 100ab70. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Release 927.0.0 (#8525) ## Explanation Release for `@metamask/messenger-cli@0.2.0`. ## 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 - [ ] 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 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** > Low risk release bookkeeping: only bumps versions and updates `@metamask/messenger-cli` changelog, with no runtime code changes. > > **Overview** > Bumps the monorepo version to `927.0.0` and releases `@metamask/messenger-cli` as `0.2.0`. > > Updates the `@metamask/messenger-cli` changelog to include the `0.2.0` entry (noting the breaking formatter option change) and adjusts compare links for the new release. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit a1ba481. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Release/926.0.0 (#8523) ## Explanation Releases a new version of the social-controllers package. Ref work: #8520 ## 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) - [x] 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** > Only version and changelog updates; no runtime code changes in this diff. Main risk is downstream consumer breakage due to the `2.0.0` major version bump. > > **Overview** > Updates release metadata: bumps the monorepo version to `926.0.0` and `@metamask/social-controllers` to `2.0.0`. > > Adds a `2.0.0` section to `social-controllers` changelog documenting **breaking** API/signature changes (removal of `addressOrUid` parameters and switch to `/v1/users/me/...` endpoints) and updates compare links accordingly. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 9ec4d19. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Release/926.0.0 (#8523) ## Explanation Releases a new version of the social-controllers package. Ref work: #8520 ## 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) - [x] 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** > Only version and changelog updates; no runtime code changes in this diff. Main risk is downstream consumer breakage due to the `2.0.0` major version bump. > > **Overview** > Updates release metadata: bumps the monorepo version to `926.0.0` and `@metamask/social-controllers` to `2.0.0`. > > Adds a `2.0.0` section to `social-controllers` changelog documenting **breaking** API/signature changes (removal of `addressOrUid` parameters and switch to `/v1/users/me/...` endpoints) and updates compare links accordingly. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 9ec4d19. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Release 927.0.0 (#8525) ## Explanation Release for `@metamask/messenger-cli@0.2.0`. ## 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 - [ ] 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 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** > Low risk release bookkeeping: only bumps versions and updates `@metamask/messenger-cli` changelog, with no runtime code changes. > > **Overview** > Bumps the monorepo version to `927.0.0` and releases `@metamask/messenger-cli` as `0.2.0`. > > Updates the `@metamask/messenger-cli` changelog to include the `0.2.0` entry (noting the breaking formatter option change) and adjusts compare links for the new release. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit a1ba481. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Release/925.0.0 (#8516) ## 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 - [ ] 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 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/changelog-only release bookkeeping with no functional code changes in this diff. > > **Overview** > Bumps the monorepo version to `925.0.0` and releases `@metamask/perps-controller` `3.2.0`. > > Updates the perps controller changelog to include the `3.2.0` entry (noting new `isAbortError` export, flip-position pricing behavior change, removal of an unused HyperLiquid fee constant, and reduced Sentry noise for expected `AbortError`s) and adjusts compare links accordingly. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 3d10b2f. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Release/924.0.0 (#8514) ## Explanation Release the chomp-api-service package <!-- 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 - [ ] 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 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** > Only version/changelog metadata changes to support a release; no runtime logic is modified. > > **Overview** > Cuts a release by bumping the root monorepo version to `924.0.0` and promoting `@metamask/chomp-api-service` from `0.0.0` to `1.0.0`. > > Updates the `chomp-api-service` changelog to include the `1.0.0` release section and fixes the compare/release links to point at the new tag. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 69c637b. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
PreviousNext