Repository navigation
Release/1375.0.0 - #11176
Merged
Merged
Release/1375.0.0#11176
Conversation
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Prithpal-Sooriya
temporarily deployed
to
default-branch
October 28, 2026 21:31 — with
GitHub Actions
Inactive
Prithpal-Sooriya
temporarily deployed
to
default-branch
October 28, 2026 21:32 — with
GitHub Actions
Inactive
Contributor
|
✅ Changelogs updated and pushed. |
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
mcmire
reviewed
Oct 28, 2026
This reverts commit 89876d5.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
|
||
| ## [Unreleased] | ||
|
|
||
| ### Changed |
Contributor
Author
There was a problem hiding this comment.
Discussed here:
#11176 (comment)
This change is internal only, non-breaking, and technically fixes a performance issue.
Reclassified changelog entry to be under ### Fixed and made this a patch release.
cryptodev-2s
approved these changes
Oct 28, 2026
4 tasks
Naz-Ovh
pushed a commit
to 0x-fork/metamask-core
that referenced
this pull request
Nov 4, 2026
Reverts MetaMask#11176 <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > Release and dependency version rollback with no runtime code changes in the diff; main risk is consumers expecting published 20.0.2/1375.0.0 artifacts. > > **Overview** > Reverts **Release/1375.0.0** ([MetaMask#11176](MetaMask#11176)) by rolling back monorepo and package versioning only—there are **no application source changes** in this diff. > > The root monorepo version goes from `1375.0.0` back to **`1374.0.0`**. **`@metamask/assets-controller`** is reverted from **`20.0.2` to `20.0.1`**: the `20.0.2` changelog section is removed and the Multicall3 `aggregate3` codec work stays under **`[Unreleased]`** as *Changed* (not a shipped patch). > > **`@metamask/bridge-controller`** and **`@metamask/transaction-pay-controller`** drop their dependency on `@metamask/assets-controller` from **`^20.0.2` to `^20.0.1`**, with matching changelog edits. **`yarn.lock`** is updated to match. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 2b2044a. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Naz-Ovh
pushed a commit
to 0x-fork/metamask-core
that referenced
this pull request
Nov 4, 2026
…sk#11191) ## Explanation The `Test (22.x)` and `Test (24.x)` jobs only ran when `github.ref_name` was `main`, or when the base ref was a release branch. Release pull requests have a `release/*` head branch and target `main`, so neither condition matched and the jobs were skipped (e.g., MetaMask#11176 only ran the Node.js 26.x tests). This adds a `github.head_ref` check so the full Node.js matrix runs for release pull requests. The `base_ref` checks stay, as they cover pull requests that target a release branch. ## References - Observed on MetaMask#11176. ## 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** > Workflow-only change to job `if` conditions; no application code or runtime behavior is affected. > > **Overview** > **Test (22.x)** and **Test (24.x)** in `lint-build-test.yml` now run when the pull request **head** branch is `release/*`, not only on `main` or when the **base** is a release branch. > > Release PRs (`release/*` → `main`) previously skipped those jobs because `github.ref_name` is the head branch and the old conditions did not treat a release head as eligible—so only Node 26.x tests ran. The existing `base_ref` / merge-group release checks are unchanged for PRs targeting release branches. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit adf8b64. 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
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 1375.0.0, bumping
@metamask/assets-controllerfrom 20.0.1 to 20.0.2 (patch).aggregate3codecs for balance batches (perf(assets-controller): add hand-rolled aggregate3 codecs #11078)@metamask/bridge-controllerand@metamask/transaction-pay-controlleronly have their@metamask/assets-controllerdependency range bumped to^20.0.2; they are intentionally not released.Checklist
yarn changelog:validatepasses🤖 Generated with Claude Code
Note
Low Risk
This PR is release bookkeeping only; the balance-batch codec behavior ships via the already-merged assets-controller 20.0.2 release, which touches on-chain balance reads but is classified as a fix with parity checks against Ethers.
Overview
Release 1375.0.0 cuts a patch release of
@metamask/assets-controllerat 20.0.2 (monorepo root version 1374.0.0 → 1375.0.0). The new changelog entry documents the shipped fix from #11078: balance batches use hand-rolled Multicall3aggregate3codecs, with Ethers codecs kept for byte-identical comparison.@metamask/bridge-controllerand@metamask/transaction-pay-controlleronly update their@metamask/assets-controllerdependency to^20.0.2and adjust changelogs; they are not version-bumped in this PR.yarn.lockis refreshed accordingly.There are no application source changes in this diff—versioning, changelog, dependency ranges, and lockfile only.
Reviewed by Cursor Bugbot for commit 880c066. Bugbot is set up for automated code reviews on this repo. Configure here.