Revert "Release 1247.0.0" - #10159
Merged
Merged
Conversation
This reverts commit f1c8f6c.
Mrtenz
temporarily deployed
to
default-branch
September 9, 2026 19:34 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
Mrtenz
enabled auto-merge
September 9, 2026 19:35
cryptodev-2s
approved these changes
Sep 9, 2026
pull Bot
pushed a commit
to Reality2byte/core
that referenced
this pull request
Sep 9, 2026
## Explanation Recreated MetaMask#10155 after reverting in MetaMask#10159. ## 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] > **High Risk** > Monorepo-wide major releases and breaking platform requirements (ESM, Node 22) force coordinated client upgrades; misaligned versions can break messenger/controller wiring at runtime. > > **Overview** > Publishes **1247.0.0** of `@metamask/core-monorepo` by cutting new major (or milestone) versions across many workspace packages and aligning their `package.json` dependency ranges. > > The release mostly **finalizes changelog entries** that were sitting under `[Unreleased]`—especially **ESM-only**, **Node.js 22+**, and **ES2022** build targets—while adding **MetaMask#10160** dependency bumps such as `@metamask/messenger` **^3**, `@metamask/base-controller` **^10**, `@metamask/network-controller` **^37**, `@metamask/transaction-controller` **^70**, and `@metamask/controller-utils` **^13**. Heavily connected packages (e.g. `assets-controller`, `assets-controllers`, `bridge-controller`, `core-backend`) get matching semver bumps so the graph stays consistent. > > The root `package.json` also bumps workspace dev dependencies on `@metamask/eth-block-tracker`, `@metamask/eth-json-rpc-provider`, `@metamask/json-rpc-engine`, and `@metamask/network-controller`. **No application/controller source changes** appear in this diff—only versions, changelogs, and dependency pins. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit ffecd7b. 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
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.
Reverts #10155.
The release workflow didn't trigger.
Note
Medium Risk
Wide dependency and semver rollback across the monorepo can desync consumers that already picked up 1247.0.0 packages until a successful re-release; runtime behavior is unchanged but install graphs and published versions need careful coordination.
Overview
Reverts the 1247.0.0 release from #10155 because the release workflow did not run. This rolls the repo back to the pre-release state without changing controller or service implementation code.
The monorepo root version moves from 1247.0.0 to 1246.0.0, and package versions are downgraded across many
@metamask/*packages (for example@metamask/base-controller10→9.1.0,@metamask/messenger3→2.x,@metamask/network-controller37→36, and similar cascades through accounts, assets, bridge, transaction, and related packages).Inter-package dependency ranges in
package.jsonfiles are aligned with those older versions, and root devDependencies such as@metamask/eth-block-tracker,@metamask/json-rpc-engine, and@metamask/network-controllerare stepped back as well. Changelogs drop the new major/minor release sections that #10155 added, fold those notes back under[Unreleased]where applicable, and fix version compare links at the bottom of each file.Reviewed by Cursor Bugbot for commit cd89c0d. Bugbot is set up for automated code reviews on this repo. Configure here.