Release 1183.0.0 - #9807
Merged
Merged
Conversation
gantunesr
marked this pull request as ready for review
August 7, 2026 19:36
gantunesr
temporarily deployed
to
default-branch
August 7, 2026 19:36 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
gantunesr
temporarily deployed
to
default-branch
August 7, 2026 19:37 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
|
✅ Changelogs updated and pushed. |
cryptodev-2s
approved these changes
Aug 7, 2026
gantunesr
enabled auto-merge
August 7, 2026 19:45
pull Bot
pushed a commit
to Reality2byte/core
that referenced
this pull request
Aug 11, 2026
## Explanation Release `1187.0.0` with a patch version bump for: - **`@metamask/transaction-controller`** `69.5.1` → `69.5.2` ### `@metamask/transaction-controller@69.5.2` #### Changed - Bump `@metamask/accounts-controller` from `^39.0.7` to `^39.1.0` ([MetaMask#9807](MetaMask#9807)) #### Fixed - Skip resimulation check when failing incomplete transactions at startup, preventing a crash when `isSimulationEnabled` depends on controllers not yet registered ([MetaMask#9821](MetaMask#9821)) ### Dependency updates 17 packages had their `@metamask/transaction-controller` dependency range updated to `^69.5.2` with corresponding changelog entries under `[Unreleased]`: `@metamask/assets-controller`, `@metamask/assets-controllers`, `@metamask/bridge-controller`, `@metamask/bridge-status-controller`, `@metamask/client-utils`, `@metamask/eip-5792-middleware`, `@metamask/gator-permissions-controller`, `@metamask/money-account-utils`, `@metamask/network-enablement-controller`, `@metamask/phishing-controller`, `@metamask/profile-metrics-controller`, `@metamask/shield-controller`, `@metamask/smart-transactions-controller`, `@metamask/subscription-controller`, `@metamask/transaction-pay-controller`, `@metamask/user-operation-controller`, `@metamask/wallet` ## References - [MetaMask#9807](MetaMask#9807) — Bump `@metamask/accounts-controller` - [MetaMask#9821](MetaMask#9821) — Skip resimulation check when failing incomplete transactions at startup ## 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 - [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** > Dependency and release-metadata only; behavioral change is limited to the patch-level transaction-controller fix already shipped in 69.5.2. > > **Overview** > **Monorepo release `1187.0.0`** bumps the root version from `1186.0.0` and publishes **`@metamask/transaction-controller` `69.5.2`** (from `69.5.1`). > > Downstream packages only change **`package.json`** dependency ranges to `^69.5.2`, **`yarn.lock`**, and **`[Unreleased]` changelog** lines (17 consumers such as `wallet`, bridge, assets, EIP-5792 middleware, etc.). There is no application source change in this diff. > > Consumers of **`69.5.2`** get the fixes documented on that release: skip the resimulation check when failing incomplete transactions at startup (avoids a crash when `isSimulationEnabled` touches controllers not registered yet), plus the `accounts-controller` bump noted in that package’s changelog. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 90794b1. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
pull Bot
pushed a commit
to Reality2byte/core
that referenced
this pull request
Aug 11, 2026
## 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? --> ## Bridge Controller [79.1.0] ### Added - Point Arc's native USDC to the registered `slip44:5042` asset ID instead of the `erc20:0x0000...` placeholder ([MetaMask#9796](MetaMask#9796)) ### Changed - Bump `@metamask/transaction-controller` from `^69.5.0` to `^69.5.2` ([MetaMask#9798](MetaMask#9798), [MetaMask#9823](MetaMask#9823)) - Bump `@metamask/accounts-controller` from `^39.0.6` to `^39.1.0` ([MetaMask#9791](MetaMask#9791), [MetaMask#9807](MetaMask#9807)) - Bump `@metamask/multichain-network-controller` from `^3.2.2` to `^3.2.3` ([MetaMask#9791](MetaMask#9791)) - Bump `@metamask/assets-controllers` from `^111.0.0` to `^111.1.0` ([MetaMask#9793](MetaMask#9793)) - Bump `@metamask/assets-controller` from `^13.1.1` to `^13.1.2` ([MetaMask#9813](MetaMask#9813)) ## 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** > No runtime code changes in the diff—only versions, changelogs, and lockfile entries for a tagged release. > > **Overview** > Release cut that bumps the core monorepo to **1188.0.0** and publishes **`@metamask/bridge-controller` 79.1.0**, with **`@metamask/bridge-status-controller`** updated to depend on bridge-controller **^79.1.0** and **`yarn.lock`** aligned. > > The **79.1.0** changelog (not new code in this diff) documents shipping Arc native USDC on **`slip44:5042`** instead of a zero-address ERC-20 placeholder, plus routine dependency bumps on transaction-controller, accounts-controller, multichain-network-controller, and assets packages. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 31a2562. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
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
2 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
Minor release of:
@metamask/accounts-controllerReferences
Checklist
Note
Low Risk
Release-only dependency alignment for a minor accounts-controller add (
clearState); wide touch surface but no behavioral changes introduced in this PR’s diff.Overview
Monorepo release 1183.0.0 that ships
@metamask/accounts-controller39.1.0 and aligns dependents on^39.1.0.The accounts-controller minor release (documented in its changelog for this bump) adds
clearState/AccountsController:clearStateto reset internal account state to defaults and exportsgetDefaultAccountsControllerState(#9799). This PR itself is version, changelog,package.json, andyarn.lockupdates across packages such aswallet,assets-controller,transaction-controller, bridge controllers, and multichain packages—no new controller logic in the diff.Reviewed by Cursor Bugbot for commit 89eecf4. Bugbot is set up for automated code reviews on this repo. Configure here.