Skip to content

Release 1055.0.0#9199

Open
amitabh94 wants to merge 2 commits into
mainfrom
release/1055.0.0
Open

Release 1055.0.0#9199
amitabh94 wants to merge 2 commits into
mainfrom
release/1055.0.0

Conversation

@amitabh94

@amitabh94 amitabh94 commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

Explanation

Current state: @metamask/ramps-controller@14.2.0 is the latest publish on npm. Since then, two consumer-facing changes merged to main but are not yet published:

Mobile QA is currently blocked on a preview build (@metamask-previews/ramps-controller) for TestFlight; we need a real npm release to drop preview/resolution pins.

Solution: Release 1055.0.0 publishes @metamask/ramps-controller@14.3.0. This PR only versions and ships what is already on main — no new feature work in the diff.

What's in 14.3.0:

Category Change
Fixed Compare internal order codes in addOrder / getOrder / addPrecreatedOrder (#9159)
Added Transak API error helpers (getTransakApiMessage, isTransakPhoneRegisteredError, transakErrorCodes.ts) (#9135)
Changed Bump @metamask/profile-sync-controller to ^28.2.0 (#9119)

SemVer: Minor bump (14.2.0 → 14.3.0) — includes new exports plus a bug fix. No breaking API changes.

Other packages / deps: Only @metamask/ramps-controller is published in this release. Dependency bumps listed above were already merged separately and are included because they landed after 14.2.0.

Worth noting for reviewers: The fix normalizes stored providerOrderId to the internal order code for polling/lookup consistency. Order Details “copy id” may show the MetaMask c-… code rather than the provider-native UUID — support should use provider link / tx hash for native references.

References

  • TRAM-3539 — duplicate Moonpay Activity rows on redirect buys
  • #9159 — internal order id merge fix
  • #9135 — Transak API error helpers
  • #9119 — profile-sync-controller dep bump
  • MetaMask/metamask-mobile#31837 — mobile QA PR (preview pin; update to ^14.3.0 after this release)

Mobile follow-up after merge + npm publish:

  1. Bump @metamask/ramps-controller to ^14.3.0
  2. Remove preview alias / resolutions / previewBuilds
  3. Re-run TestFlight QA for Moonpay redirect buy (single Activity row)

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
  • I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them (N/A — no breaking changes)

Note

Low Risk
Release-only version, changelog, and lockfile updates with no runtime code changes in this diff.

Overview
Release 1055.0.0 publishes @metamask/ramps-controller@14.3.0 to npm. The PR diff is versioning and dependency wiring only—no new feature code.

@metamask/ramps-controller goes 14.2.0 → 14.3.0 with changelog section 14.3.0 (content already on main): Transak error helpers (getTransakApiMessage, isTransakPhoneRegisteredError, transakErrorCodes.ts), bump to @metamask/profile-sync-controller ^28.2.0, and the documented order-id merge fix for duplicate Moonpay Activity rows.

Root package.json is bumped 1054.0.0 → 1055.0.0. @metamask/transaction-pay-controller updates its dependency to @metamask/ramps-controller ^14.3.0 and records that in its changelog; yarn.lock is updated accordingly.

Reviewed by Cursor Bugbot for commit 4685db4. Bugbot is set up for automated code reviews on this repo. Configure here.

@amitabh94 amitabh94 requested review from a team as code owners June 18, 2026 23:51
@amitabh94 amitabh94 deployed to default-branch June 18, 2026 23:52 — with GitHub Actions Active
@amitabh94 amitabh94 enabled auto-merge June 18, 2026 23:52
@mm-token-exchange-service

Copy link
Copy Markdown

✅ Changelogs updated and pushed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants