Release 958.0.0#8691
Merged
matthewwalsh0 merged 2 commits intomainfrom May 5, 2026
Merged
Conversation
matthewwalsh0
force-pushed
the
release/958.0.0
branch
from
e1cf722 to
62a9484
Compare
matthewwalsh0
force-pushed
the
release/958.0.0
branch
from
62a9484 to
6c8b41b
Compare
cryptodev-2s
approved these changes
May 5, 2026
Merged
pull Bot
pushed a commit
to dmrazzy/core
that referenced
this pull request
May 5, 2026
## Summary This release PR publishes `@metamask/ramps-controller@13.3.0`, which includes the circuit-breaker error-key fix from [MetaMask#8596](MetaMask#8596) and the other unreleased ramps-controller changes accumulated since `13.2.0`. ## Why this is separate This is the successor to [MetaMask#8692](MetaMask#8692). That PR was originally cut as `Release/958.0.0`, but [MetaMask#8691](MetaMask#8691) merged first and consumed `958.0.0`, so this re-cuts the same content as `Release/959.0.0` from current `main`. ## What changed - bump the monorepo release version to `959.0.0` - publish `@metamask/ramps-controller@13.3.0` - move the current ramps-controller unreleased entries into the `13.3.0` changelog section - update `@metamask/transaction-pay-controller` to depend on `@metamask/ramps-controller@^13.3.0` ## Why the transaction-pay-controller range update is included `transaction-pay-controller` is the in-repo consumer of `@metamask/ramps-controller`. Once ramps-controller is versioned to `13.3.0`, the monorepo dependency constraints require the internal dependency range to move from `^13.2.0` to `^13.3.0` as well. This keeps the repo internally consistent without broadening the published package scope. ## Validation - `yarn install` (regenerates `yarn.lock`) - `yarn constraints` - `yarn lint:dependencies` - `yarn lint:misc:check` - `yarn workspace @metamask/ramps-controller changelog:validate` - `yarn workspace @metamask/transaction-pay-controller changelog:validate` - `yarn workspace @metamask/ramps-controller build` 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > Low risk release bookkeeping: version bumps, changelog cut, and an internal dependency range update with no functional code changes in this diff. > > **Overview** > Bumps the monorepo version to `959.0.0` and publishes `@metamask/ramps-controller@13.3.0` by cutting the existing *Unreleased* changelog entries into a new `13.3.0` section. > > Updates `@metamask/transaction-pay-controller` to depend on `@metamask/ramps-controller@^13.3.0`, with corresponding `yarn.lock` changes to keep workspace constraints consistent. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 90e73f1. 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: Claude Sonnet 4.6 <noreply@anthropic.com>
pull Bot
pushed a commit
to dmrazzy/core
that referenced
this pull request
May 5, 2026
> [!NOTE] > This is a repeat of MetaMask#8698 because the release workflow was not triggered correctly. ## Summary This release PR publishes `@metamask/ramps-controller@13.3.0`, which includes the circuit-breaker error-key fix from [MetaMask#8596](MetaMask#8596) and the other unreleased ramps-controller changes accumulated since `13.2.0`. ## Why this is separate This is the successor to [MetaMask#8692](MetaMask#8692). That PR was originally cut as `Release/958.0.0`, but [MetaMask#8691](MetaMask#8691) merged first and consumed `958.0.0`, so this re-cuts the same content as `Release/959.0.0` from current `main`. ## What changed - bump the monorepo release version to `959.0.0` - publish `@metamask/ramps-controller@13.3.0` - move the current ramps-controller unreleased entries into the `13.3.0` changelog section - update `@metamask/transaction-pay-controller` to depend on `@metamask/ramps-controller@^13.3.0` ## Why the transaction-pay-controller range update is included `transaction-pay-controller` is the in-repo consumer of `@metamask/ramps-controller`. Once ramps-controller is versioned to `13.3.0`, the monorepo dependency constraints require the internal dependency range to move from `^13.2.0` to `^13.3.0` as well. This keeps the repo internally consistent without broadening the published package scope. ## Validation - `yarn install` (regenerates `yarn.lock`) - `yarn constraints` - `yarn lint:dependencies` - `yarn lint:misc:check` - `yarn workspace @metamask/ramps-controller changelog:validate` - `yarn workspace @metamask/transaction-pay-controller changelog:validate` - `yarn workspace @metamask/ramps-controller build` 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > Low risk release bookkeeping: version/changelog updates and an internal dependency range bump, with no functional code changes in this diff. > > **Overview** > Bumps the monorepo release version to `959.0.0` and publishes `@metamask/ramps-controller@13.3.0` by moving the previously *Unreleased* ramps entries into a new `13.3.0` changelog section and updating compare links. > > Updates the in-repo consumer `@metamask/transaction-pay-controller` to depend on `@metamask/ramps-controller@^13.3.0`, with corresponding `yarn.lock` adjustments. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 45b6091. 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: saustrie-consensys <shane.austrie@consensys.net> Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.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.
Minor release of
@metamask/transaction-controller.Note
Low Risk
Mostly version/changelog updates with no functional code changes in this PR; risk is limited to downstream behavior changes introduced by the new
@metamask/transaction-controller@65.1.0dependency.Overview
Cuts release
958.0.0by bumping@metamask/transaction-controllerto65.1.0and propagating the dependency range update (^65.0.0→^65.1.0) across affected packages (e.g. assets/bridge/phishing/subscription/user-operation controllers).Updates package changelogs (and
yarn.lock) to reflect the newtransaction-controllerversion, including adding the65.1.0section and link targets inpackages/transaction-controller/CHANGELOG.md.Reviewed by Cursor Bugbot for commit 6c8b41b. Bugbot is set up for automated code reviews on this repo. Configure here.