Release/662.0.0

[sahar-fehri]

Explanation

Minor release for assets-controllers.

References

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, highlighting breaking changes as necessary
• I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes

---

Note

Release assets-controllers 87.1.0 with trending tokens API and bump monorepo to 662.0.0; update dependent packages to use the new version.

• Packages:
  • @metamask/assets-controllers → 87.1.0
    • Added getTrendingTokens API and new types SortTrendingBy, TrendingAsset (changelog).
  • Bump devDeps to @metamask/assets-controllers@^87.1.0 in:
    • packages/bridge-controller/package.json
    • packages/transaction-pay-controller/package.json
• Repo:
  • Monorepo version → 662.0.0 in root package.json.
  • Update packages/assets-controllers/CHANGELOG.md links and yarn.lock entries accordingly.

^{Written by Cursor Bugbot for commit 8c30bb3. This will update automatically on new commits. Configure here.}

[cursor]

Bug: Inconsistent Dependency Versions Across Packages Updated Separately

Inconsistent dependency version for @metamask/assets-controllers. The devDependencies was updated to ^87.1.0 but the peerDependencies remains at ^87.0.0. Both should be updated together to maintain consistency, especially in a monorepo where packages are released together.

 

[cursor]

Bug: Inconsistent Dependency Versions Across Packages

Inconsistent dependency version for @metamask/assets-controllers. The devDependencies was updated to ^87.1.0 but the peerDependencies remains at ^87.0.0. Both should be updated together to maintain consistency, especially in a monorepo where packages are released together.

 

[cryptodev-2s]

LGTM!