Release/691.0.0 (#7220)

## Explanation

<!--
Thanks for your contribution! Take a moment to answer these questions so
that reviewers have the information they need to properly understand
your changes:

* What is the current state of things and why does it need to change?
* What is the solution your changes offer and how does it work?
* Are there any changes whose purpose might not obvious to those
unfamiliar with the domain?
* If your primary goal was to update one package but you found you had
to update another one along the way, why did you do so?
* If you had to upgrade a dependency, why did you do so?
-->
Minor release of @metamask/transaction-controller. Added
`musdConversion` transaction type.

## References

<!--
Are there any issues that this pull request is tied to?
Are there other links that reviewers should consult to understand these
changes better?
Are there client or consumer pull requests to adopt any breaking
changes?

For example:

* Fixes #12345
* Related to #67890
-->

## 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](https://github.com/MetaMask/core/tree/main/docs/contributing.md#updating-changelogs)
- [ ] I've introduced [breaking
changes](https://github.com/MetaMask/core/tree/main/docs/breaking-changes.md)
in this PR and have prepared draft pull requests for clients and
consumer packages to resolve them

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> Releases 691.0.0, publishing @metamask/transaction-controller 62.2.0
(adds `musdConversion` type) and updating all dependents to ^62.2.0 with
corresponding changelog entries.
> 
> - **Core**
>   - Bump monorepo version to `691.0.0`.
> - **Transaction Controller**
> - Release `@metamask/[email protected]` adding
`musdConversion` transaction type.
> - **Dependents updated to `^62.2.0`**
> - `@metamask/assets-controllers`, `bridge-controller`,
`bridge-status-controller`, `eip-5792-middleware`,
`gator-permissions-controller`, `network-enablement-controller`,
`phishing-controller`, `shield-controller`, `subscription-controller`,
`transaction-pay-controller`, `user-operation-controller`, and devDep in
`earn-controller`.
> - **Changelogs**
> - Note dependency bumps and continued migration of peer deps to direct
deps (refs `#7209`, `#7220`).
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
b7997e5. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

Author: Matt561

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@metamask/core-monorepo",
-  "version": "690.0.0",
+  "version": "691.0.0",
   "private": true,
   "description": "Monorepo for packages shared between MetaMask clients",
   "repository": {

packages/assets-controllers/CHANGELOG.md

@@ -18,7 +18,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Changed
 
-- Move peer dependencies for controller and service packages to direct dependencies ([#7209](https://github.com/MetaMask/core/pull/7209))
+- Move peer dependencies for controller and service packages to direct dependencies ([#7209](https://github.com/MetaMask/core/pull/7209), [#7220](https://github.com/MetaMask/core/pull/7220))
   - The dependencies moved are:
     - `@metamask/account-tree-controller` (^4.0.0)
     - `@metamask/accounts-controller` (^35.0.0)
@@ -32,7 +32,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
     - `@metamask/preferences-controller` (^22.0.0)
     - `@metamask/profile-sync-controller` (^27.0.0)
     - `@metamask/snaps-controllers` (^14.0.1)
-    - `@metamask/transaction-controller` (^62.1.0)
+    - `@metamask/transaction-controller` (^62.2.0)
   - In clients, it is now possible for multiple versions of these packages to exist in the dependency tree.
     - For example, this scenario would be valid: a client relies on `@metamask/controller-a` 1.0.0 and `@metamask/controller-b` 1.0.0, and `@metamask/controller-b` depends on `@metamask/controller-a` 1.1.0.
   - Note, however, that the versions specified in the client's `package.json` always "win", and you are expected to keep them up to date so as not to break controller and service intercommunication.

packages/assets-controllers/package.json

@@ -78,7 +78,7 @@
     "@metamask/snaps-controllers": "^14.0.1",
     "@metamask/snaps-sdk": "^9.0.0",
     "@metamask/snaps-utils": "^11.0.0",
-    "@metamask/transaction-controller": "^62.1.0",
+    "@metamask/transaction-controller": "^62.2.0",
     "@metamask/utils": "^11.8.1",
     "@types/bn.js": "^5.1.5",
     "@types/uuid": "^8.3.0",

packages/bridge-controller/CHANGELOG.md

@@ -9,14 +9,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Changed
 
-- Move peer dependencies for controller and service packages to direct dependencies ([#7209](https://github.com/MetaMask/core/pull/7209))
+- Move peer dependencies for controller and service packages to direct dependencies ([#7209](https://github.com/MetaMask/core/pull/7209), [#7220](https://github.com/MetaMask/core/pull/7220))
   - The dependencies moved are:
     - `@metamask/accounts-controller` (^35.0.0)
     - `@metamask/assets-controllers` (^91.0.0)
     - `@metamask/network-controller` (^26.0.0)
     - `@metamask/remote-feature-flag-controller` (^2.0.1)
     - `@metamask/snaps-controllers` (^14.0.0)
-    - `@metamask/transaction-controller` (^62.1.0)
+    - `@metamask/transaction-controller` (^62.2.0)
   - In clients, it is now possible for multiple versions of these packages to exist in the dependency tree.
     - For example, this scenario would be valid: a client relies on `@metamask/controller-a` 1.0.0 and `@metamask/controller-b` 1.0.0, and `@metamask/controller-b` depends on `@metamask/controller-a` 1.1.0.
   - Note, however, that the versions specified in the client's `package.json` always "win", and you are expected to keep them up to date so as not to break controller and service intercommunication.

packages/bridge-controller/package.json

@@ -66,7 +66,7 @@
     "@metamask/polling-controller": "^16.0.0",
     "@metamask/remote-feature-flag-controller": "^2.0.1",
     "@metamask/snaps-controllers": "^14.0.1",
-    "@metamask/transaction-controller": "^62.1.0",
+    "@metamask/transaction-controller": "^62.2.0",
     "@metamask/utils": "^11.8.1",
     "bignumber.js": "^9.1.2",
     "reselect": "^5.1.1",

packages/bridge-status-controller/CHANGELOG.md

@@ -9,14 +9,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Changed
 
-- Move peer dependencies for controller and service packages to direct dependencies ([#7209](https://github.com/MetaMask/core/pull/7209))
+- Move peer dependencies for controller and service packages to direct dependencies ([#7209](https://github.com/MetaMask/core/pull/7209), [#7220](https://github.com/MetaMask/core/pull/7220))
   - The dependencies moved are:
     - `@metamask/accounts-controller` (^35.0.0)
     - `@metamask/bridge-controller` (^63.0.0)
     - `@metamask/gas-fee-controller` (^26.0.0)
     - `@metamask/network-controller` (^26.0.0)
     - `@metamask/snaps-controllers` (^14.0.1)
-    - `@metamask/transaction-controller` (^62.1.0)
+    - `@metamask/transaction-controller` (^62.2.0)
   - In clients, it is now possible for multiple versions of these packages to exist in the dependency tree.
     - For example, this scenario would be valid: a client relies on `@metamask/controller-a` 1.0.0 and `@metamask/controller-b` 1.0.0, and `@metamask/controller-b` depends on `@metamask/controller-a` 1.1.0.
   - Note, however, that the versions specified in the client's `package.json` always "win", and you are expected to keep them up to date so as not to break controller and service intercommunication.

packages/bridge-status-controller/package.json

@@ -57,7 +57,7 @@
     "@metamask/polling-controller": "^16.0.0",
     "@metamask/snaps-controllers": "^14.0.1",
     "@metamask/superstruct": "^3.1.0",
-    "@metamask/transaction-controller": "^62.1.0",
+    "@metamask/transaction-controller": "^62.2.0",
     "@metamask/utils": "^11.8.1",
     "bignumber.js": "^9.1.2",
     "uuid": "^8.3.2"

packages/earn-controller/package.json

@@ -61,7 +61,7 @@
   },
   "devDependencies": {
     "@metamask/auto-changelog": "^3.4.4",
-    "@metamask/transaction-controller": "^62.1.0",
+    "@metamask/transaction-controller": "^62.2.0",
     "@ts-bridge/cli": "^0.6.4",
     "@types/jest": "^27.4.1",
     "deepmerge": "^4.2.2",

packages/eip-5792-middleware/CHANGELOG.md

@@ -9,7 +9,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Changed
 
-- Bump `@metamask/transaction-controller` from `^61.3.0` to `^62.1.0` ([#7007](https://github.com/MetaMask/core/pull/7007), [#7126](https://github.com/MetaMask/core/pull/7126), [#7153](https://github.com/MetaMask/core/pull/7153), [#7202](https://github.com/MetaMask/core/pull/7202), [#7215](https://github.com/MetaMask/core/pull/7202))
+- Bump `@metamask/transaction-controller` from `^61.3.0` to `^62.2.0` ([#7007](https://github.com/MetaMask/core/pull/7007), [#7126](https://github.com/MetaMask/core/pull/7126), [#7153](https://github.com/MetaMask/core/pull/7153), [#7202](https://github.com/MetaMask/core/pull/7202), [#7215](https://github.com/MetaMask/core/pull/7202), [#7220](https://github.com/MetaMask/core/pull/7220))
 
 ## [2.0.0]
 

packages/eip-5792-middleware/package.json

@@ -50,7 +50,7 @@
   "dependencies": {
     "@metamask/messenger": "^0.3.0",
     "@metamask/superstruct": "^3.1.0",
-    "@metamask/transaction-controller": "^62.1.0",
+    "@metamask/transaction-controller": "^62.2.0",
     "@metamask/utils": "^11.8.1",
     "lodash": "^4.17.21",
     "uuid": "^8.3.2"