Release 1094.0.0#9392
Merged
Merged
Conversation
FrederikBolding
temporarily deployed
to
default-branch
GitHub Actions
Inactive
FrederikBolding
temporarily deployed
to
default-branch
GitHub Actions
Inactive
|
✅ Changelogs updated and pushed. |
cryptodev-2s
approved these changes
Jul 6, 2026
wenfix
approved these changes
Jul 6, 2026
pull Bot
pushed a commit
to dmrazzy/core
that referenced
this pull request
Jul 7, 2026
## Explanation Releases two packages needed to fix stuck/underpriced bridge smart transactions in the clients (extension + mobile). ### `@metamask/transaction-controller` — `68.2.2` → `68.3.0` (minor) - **Added:** `failTransaction` method + `TransactionController:failTransaction` messenger action ([MetaMask#9400](MetaMask#9400)) — fails a tx through the standard path, emitting `transactionFailed`/`transactionStatusUpdated`/`transactionFinished`. - **Fixed:** Only apply user-saved (advanced) gas fees to dApp transactions; ignored for internal (`isInternal`) txs such as swaps and bridges ([MetaMask#9401](MetaMask#9401)). - **Changed:** Bump `@metamask/messenger` `^1.2.0` → `^2.0.0` ([MetaMask#9392](MetaMask#9392)). ### `@metamask/smart-transactions-controller` — `24.2.4` → `25.0.0` (major) - **Changed (BREAKING):** Fail the associated regular transaction via `TransactionController:failTransaction` instead of `updateTransaction` when a smart transaction is cancelled ([MetaMask#9400](MetaMask#9400)). Consumers must now grant the STX messenger access to `TransactionController:failTransaction`. - **Changed:** Bump `@metamask/messenger` `^1.2.0` → `^2.0.0` ([MetaMask#9392](MetaMask#9392)). All other changed packages are `intentionally-skip` (owned by other teams); dependent version ranges were updated automatically. ## References - Fixes stuck-pending bridge STX (root cause in MetaMask#9400) and underpriced bridge gas (MetaMask#9401). ## Checklist - [x] I've followed the [release process](https://github.com/MetaMask/core/blob/main/docs/processes/releasing.md) - [x] Changelogs reviewed and categorized (no `Uncategorized`; breaking change marked) - [x] Version bumps follow SemVer (STX major for the breaking messenger change) <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Medium Risk** > Touches transaction failure signaling and gas on internal bridge flows; STX **25.0.0** is a breaking messenger permission change for extension/mobile integrators. > > **Overview** > **Monorepo release `1102.0.0`** that publishes **`@metamask/transaction-controller` `68.3.0`** and **`@metamask/smart-transactions-controller` `25.0.0`**, and rolls **`@metamask/transaction-controller` `^68.2.2` → `^68.3.0`** through dependent packages and **`yarn.lock`**. > > **`transaction-controller` `68.3.0`** (documented in its changelog for this release): adds **`failTransaction`** / **`TransactionController:failTransaction`** so out-of-band failures emit normal lifecycle events; fixes **advanced gas fees** so they apply only to dApp txs, not **`isInternal`** bridge/swap txs. > > **`smart-transactions-controller` `25.0.0` (breaking):** on smart-tx cancel, calls **`failTransaction`** instead of **`updateTransaction`**; hosts must delegate **`TransactionController:failTransaction`** on the STX messenger. > > Other touched packages in the diff are mainly **version/changelog dependency bumps** tied to this release, not new feature code in those files. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit c423a08. 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>
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
3 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
Release PR for a breaking change to
messenger.Note
Medium Risk
A semver-major bump to the shared messenger library touches most controllers and services; the breaking CLI removal can break release/tooling scripts until clients switch to
@metamask/messenger-cli.Overview
Monorepo release 1094.0.0 rolls out
@metamask/messenger2.0.0 across the workspace: root and dependent packages move from^1.2.0to^2.0.0, with matching Unreleased changelog lines (#9392).The
messengerpackage is versioned 2.0.0 in this release (changelog section promoted from Unreleased). That major includes breaking removal of the in-packagegenerate-action-typesCLI in favor of@metamask/messenger-cli(messenger-action-types), plus additions likegetRegisteredActionTypesandbuildChild(already documented under the 2.0.0 heading).Consumers upgrading the monorepo or individual
@metamask/*packages must align on messenger 2.x and update any scripts still invoking the old CLI.Reviewed by Cursor Bugbot for commit 41a142d. Bugbot is set up for automated code reviews on this repo. Configure here.