chore: Update RampsController to expose all methods through messenger#8221
Merged
Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
mcmire
reviewed
Mar 17, 2026
Co-authored-by: Elliot Winkler <elliot.winkler@gmail.com>
GuillaumeRx
approved these changes
Mar 18, 2026
georgeweiler
approved these changes
Mar 19, 2026
github-merge-queue Bot
pushed a commit
that referenced
this pull request
Mar 20, 2026
## Explanation This PR cuts **monorepo release `875.0.0`** and publishes a new **`@metamask/ramps-controller`** version so consumers can pick up ramps work that is already on `main` but was **not** included in the previous npm publish train. **Current state** - `main` includes ramps updates (notably messenger exposure and `getOrder` wallet/query handling), documented under **Unreleased** in `packages/ramps-controller/CHANGELOG.md`. - Without a release, clients stay on the last published `@metamask/ramps-controller` and do not get those fixes/features from the registry. **What this change does** - Bumps the monorepo root version to **`875.0.0`** (release branch convention). - Releases **`@metamask/ramps-controller@12.0.1`**, with changelog entries moved from **Unreleased** into **`[12.0.1]`** per [Keep a Changelog](https://keepachangelog.com/). - **Added:** public `RampsController` methods exposed via the messenger ([#8221](#8221)). - **Fixed:** `getOrder` wallet handling so requests and `orderStatusChanged` payloads stay consistent ([#8251](#8251)). **Note for reviewers** - If this branch also bumps **other** workspace packages (lockfile / dependents), that is to satisfy release tooling and dependency constraints for anything else selected for **875**—not arbitrary scope creep. --- ## References - Ramps fixes / API surface: [#8221](#8221), [#8251](#8251) - Internal tracking (if applicable): **TRAM-3349** - Changelog guidelines: [updating changelogs](https://github.com/MetaMask/core/tree/main/docs/processes/updating-changelogs.md) - Consumer follow-up: bump `@metamask/ramps-controller` in **MetaMask mobile/extension** (and any other consumers) after this version is on npm --- ## Checklist - [ ] I've updated the test suite for new or updated code as appropriate _(N/A — release-only if no code changes on this branch)_ - [ ] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate _(N/A unless this PR adds docs)_ - [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 _(unchecked — **patch** release; no breaking changes expected)_ --- <!-- CURSOR_SUMMARY --> > [!NOTE] > **Low Risk** > Low risk release-only change: version bumps and changelog/link updates with no functional code modifications. > > **Overview** > Cuts the monorepo release by bumping the root version to `875.0.0`. > > Publishes a patch release of `@metamask/ramps-controller` (`12.0.1`) by bumping its package version and moving the existing *Unreleased* changelog entries into a new `12.0.1` section, updating the compare links accordingly. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 5b33da9. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=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
4 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
This updates the
RampsControllerto expose all methods through the messenger in a standardised way.References
Checklist
Note
Low Risk
Mostly additive, type-only changes plus changelog updates; low risk aside from potential downstream TypeScript type/export or build issues if consumers rely on these new action types.
Overview
Adds a new auto-generated
RampsControllermessenger action type surface. IntroducesRampsController-method-action-types.ts, defining action types (and aRampsControllerMethodActionsunion) that mapRampsController:*action names to their correspondingRampsControllermethod handlers, including Transak-specific methods.Updates the
ramps-controllerchangelog to document that all publicRampsControllermethods are now exposed via the messenger and that the corresponding action types are exported.Written by Cursor Bugbot for commit 26c306d. This will update automatically on new commits. Configure here.