Skip to content

Release/691.0.0 #7220

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Nov 21, 2025
+53 −46
Merged

Release/691.0.0 #7220

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
9f26a99
Initialize Release 691.0.0
Matt561 Nov 21, 2025
e395de6
Update Release 691.0.0
Matt561 Nov 21, 2025
f7b4abf
chore: updated changelogs
Matt561 Nov 21, 2025
92a5f0d
chore: cleaning up changelogs based on pr comments
Matt561 Nov 21, 2025
b7997e5
Merge branch 'main' into release/691.0.0
Matt561 Nov 21, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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": {
Expand Down
4 changes: 2 additions & 2 deletions packages/assets-controllers/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)
Expand All @@ -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.
Expand Down
2 changes: 1 addition & 1 deletion packages/assets-controllers/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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",
Expand Down
4 changes: 2 additions & 2 deletions packages/bridge-controller/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
2 changes: 1 addition & 1 deletion packages/bridge-controller/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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",
Expand Down
4 changes: 2 additions & 2 deletions packages/bridge-status-controller/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
2 changes: 1 addition & 1 deletion packages/bridge-status-controller/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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"
Expand Down
2 changes: 1 addition & 1 deletion packages/earn-controller/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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",
Expand Down
2 changes: 1 addition & 1 deletion packages/eip-5792-middleware/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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]

Expand Down
2 changes: 1 addition & 1 deletion packages/eip-5792-middleware/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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"
Expand Down
4 changes: 2 additions & 2 deletions packages/gator-permissions-controller/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,10 +9,10 @@ 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/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.
Expand Down
2 changes: 1 addition & 1 deletion packages/gator-permissions-controller/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,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"
},
"devDependencies": {
Expand Down
4 changes: 2 additions & 2 deletions packages/network-enablement-controller/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,11 +9,11 @@ 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/multichain-network-controller` (^3.0.0)
- `@metamask/network-controller` (^26.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.
Expand Down
2 changes: 1 addition & 1 deletion packages/network-enablement-controller/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@
"@metamask/messenger": "^0.3.0",
"@metamask/multichain-network-controller": "^3.0.0",
"@metamask/network-controller": "^26.0.0",
"@metamask/transaction-controller": "^62.1.0",
"@metamask/transaction-controller": "^62.2.0",
"@metamask/utils": "^11.8.1",
"reselect": "^5.1.1"
},
Expand Down
4 changes: 4 additions & 0 deletions packages/phishing-controller/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

### Changed

- Bump `@metamask/transaction-controller` from `^62.1.0` to `^62.2.0` ([#7220](https://github.com/MetaMask/core/pull/7220))

## [16.1.0]

### Added
Expand Down
2 changes: 1 addition & 1 deletion packages/phishing-controller/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@
"@metamask/base-controller": "^9.0.0",
"@metamask/controller-utils": "^11.16.0",
"@metamask/messenger": "^0.3.0",
"@metamask/transaction-controller": "^62.1.0",
"@metamask/transaction-controller": "^62.2.0",
"@noble/hashes": "^1.8.0",
"@types/punycode": "^2.1.0",
"ethereum-cryptography": "^2.1.2",
Expand Down
4 changes: 2 additions & 2 deletions packages/shield-controller/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,10 +9,10 @@ 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/signature-controller` (^37.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.
Expand Down
2 changes: 1 addition & 1 deletion packages/shield-controller/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@
"@metamask/controller-utils": "^11.16.0",
"@metamask/messenger": "^0.3.0",
"@metamask/signature-controller": "^37.0.0",
"@metamask/transaction-controller": "^62.1.0",
"@metamask/transaction-controller": "^62.2.0",
"@metamask/utils": "^11.8.1",
"cockatiel": "^3.1.2"
},
Expand Down
2 changes: 1 addition & 1 deletion packages/subscription-controller/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,13 +9,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

### Changed

- Bump `@metamask/transaction-controller` from `^62.0.0` to `^62.2.0` ([#7215](https://github.com/MetaMask/core/pull/7215), [#7220](https://github.com/MetaMask/core/pull/7220))
- Move peer dependencies for controller and service packages to direct dependencies ([#7209](https://github.com/MetaMask/core/pull/7209))
- The dependencies moved are:
- `@metamask/profile-sync-controller` (^27.0.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.
- Bump `@metamask/transaction-controller` from `^62.0.0` to `^62.1.0` ([#7215](https://github.com/MetaMask/core/pull/7215))

## [5.0.0]

Expand Down
2 changes: 1 addition & 1 deletion packages/subscription-controller/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@
"@metamask/messenger": "^0.3.0",
"@metamask/polling-controller": "^16.0.0",
"@metamask/profile-sync-controller": "^27.0.0",
"@metamask/transaction-controller": "^62.1.0",
"@metamask/transaction-controller": "^62.2.0",
"@metamask/utils": "^11.8.1",
"bignumber.js": "^9.1.2"
},
Expand Down
5 changes: 4 additions & 1 deletion packages/transaction-controller/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

## [62.2.0]

### Added

- Add `musdConversion` transaction type ([#7218](https://github.com/MetaMask/core/pull/7218))
Expand Down Expand Up @@ -1977,7 +1979,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

All changes listed after this point were applied to this package following the monorepo conversion.

[Unreleased]: https://github.com/MetaMask/core/compare/@metamask/transaction-controller@62.1.0...HEAD
[Unreleased]: https://github.com/MetaMask/core/compare/@metamask/transaction-controller@62.2.0...HEAD
[62.2.0]: https://github.com/MetaMask/core/compare/@metamask/transaction-controller@62.1.0...@metamask/transaction-controller@62.2.0
[62.1.0]: https://github.com/MetaMask/core/compare/@metamask/transaction-controller@62.0.0...@metamask/transaction-controller@62.1.0
[62.0.0]: https://github.com/MetaMask/core/compare/@metamask/transaction-controller@61.3.0...@metamask/transaction-controller@62.0.0
[61.3.0]: https://github.com/MetaMask/core/compare/@metamask/transaction-controller@61.2.0...@metamask/transaction-controller@61.3.0
Expand Down
2 changes: 1 addition & 1 deletion packages/transaction-controller/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@metamask/transaction-controller",
"version": "62.1.0",
"version": "62.2.0",
"description": "Stores transactions alongside their periodically updated statuses and manages interactions such as approval and cancellation",
"keywords": [
"MetaMask",
Expand Down
4 changes: 2 additions & 2 deletions packages/transaction-pay-controller/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,15 +9,15 @@ 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/assets-controllers` (^91.0.0)
- `@metamask/bridge-controller` (^63.0.0)
- `@metamask/bridge-status-controller` (^63.0.0)
- `@metamask/gas-fee-controller` (^26.0.0)
- `@metamask/network-controller` (^26.0.0)
- `@metamask/remote-feature-flag-controller` (^2.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.
Expand Down
2 changes: 1 addition & 1 deletion packages/transaction-pay-controller/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@
"@metamask/metamask-eth-abis": "^3.1.1",
"@metamask/network-controller": "^26.0.0",
"@metamask/remote-feature-flag-controller": "^2.0.1",
"@metamask/transaction-controller": "^62.1.0",
"@metamask/transaction-controller": "^62.2.0",
"@metamask/utils": "^11.8.1",
"bignumber.js": "^9.1.2",
"bn.js": "^5.2.1",
Expand Down
4 changes: 2 additions & 2 deletions packages/user-operation-controller/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,13 +9,13 @@ 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/approval-controller` (^8.0.0)
- `@metamask/gas-fee-controller` (^26.0.0)
- `@metamask/keyring-controller` (^25.0.0)
- `@metamask/network-controller` (^26.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.
Expand Down
2 changes: 1 addition & 1 deletion packages/user-operation-controller/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@
"@metamask/polling-controller": "^16.0.0",
"@metamask/rpc-errors": "^7.0.2",
"@metamask/superstruct": "^3.1.0",
"@metamask/transaction-controller": "^62.1.0",
"@metamask/transaction-controller": "^62.2.0",
"@metamask/utils": "^11.8.1",
"bn.js": "^5.2.1",
"immer": "^9.0.6",
Expand Down
Loading
Loading