Release/1175.0.0

[georgeweiler]

Explanation

Releasing @metamask/client-utils@2.0.0 to ship the breaking ramp activity chainId change from #9777.

Changes

• @metamask/client-utils 1.6.0 → 2.0.0
  • BREAKING: rampBuy / rampSell ActivityItem variants require chainId; mapRampsOrder returns null when no CAIP chain can be resolved
  • Dependency bumps for @metamask/transaction-controller and @metamask/core-backend already present under Unreleased

Client follow-ups

• Extension: chore: bump @metamask/client-utils to ^2.0.0 metamask-extension#45143
• Mobile: chore(ramps): require chainId for addPrecreatedOrder (Core #9777 preview) metamask-mobile#34246 (ramps-controller side already shipped in 20.0.0)

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

Made with Cursor

[metamask-ci]

✅ No changelog changes needed.

[n3ps]

Since we're back to pre-1.4.0 behavior and no client used the versions that affected chainId and, I don't think we necessarily need to call this a "2.0.0".

When chainId was modified it was 1.3.0 -> 1.4.0 anyway 🤷