Release/699.0.0 (#7258)

cryptodev-2s · web-flow · commit 330dd1ae5b93 · 2025-11-27T20:33:39.000Z
## Explanation  ## References Mobile PR MetaMask/metamask-mobile#22911 Extension PR MetaMask/metamask-extension#37966  ## Checklist - [x] I've updated the test suite for new or updated code as appropriate - [x] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate - [x] 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) - [x] 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  --- > [!NOTE] > Bumps `@metamask/network-controller` to `^27.0.0` across the monorepo and publishes its 27.0.0 release, preparing monorepo version `699.0.0`. > > - **Network Controller (`packages/network-controller`)**: > - Release `27.0.0`: adds `NetworkController:rpcEndpointChainAvailable` event and splits payloads for degraded/unavailable events; updates changelog links. > - Bump package version to `27.0.0`. > - **Dependencies**: > - Upgrade `@metamask/network-controller` to `^27.0.0` across packages (e.g., `accounts-controller`, `assets-controllers`, `bridge-controller`, `bridge-status-controller`, `chain-agnostic-permission`, `earn-controller`, `ens-controller`, `eth-json-rpc-middleware`, `gas-fee-controller`, `multichain-api-middleware`, `multichain-network-controller`, `network-enablement-controller`, `polling-controller`, `sample-controllers`, `selected-network-controller`, `signature-controller`, `transaction-controller`, `transaction-pay-controller`, `user-operation-controller`). > - Changelogs updated to reflect the bump and prior move of peer deps to direct deps. > - **Monorepo**: > - Bump root `version` to `699.0.0` in `package.json`. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 5934c88. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup>
diff --git a/package.json b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@metamask/core-monorepo",
-  "version": "698.0.0",
+  "version": "699.0.0",
   "private": true,
   "description": "Monorepo for packages shared between MetaMask clients",
   "repository": {
@@ -63,7 +63,7 @@
     "@metamask/eth-block-tracker": "^15.0.0",
     "@metamask/eth-json-rpc-provider": "^6.0.0",
     "@metamask/json-rpc-engine": "^10.2.0",
-    "@metamask/network-controller": "^26.0.0",
+    "@metamask/network-controller": "^27.0.0",
     "@metamask/utils": "^11.8.1",
     "@ts-bridge/cli": "^0.6.4",
     "@types/jest": "^27.4.1",
diff --git a/packages/accounts-controller/CHANGELOG.md b/packages/accounts-controller/CHANGELOG.md
@@ -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), [#7258](https://github.com/MetaMask/core/pull/7258))
   - The dependencies moved are:
     - `@metamask/keyring-controller` (^25.0.0)
-    - `@metamask/network-controller` (^26.0.0)
+    - `@metamask/network-controller` (^27.0.0)
     - `@metamask/snaps-controllers` (^14.0.1)
   - 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.
diff --git a/packages/accounts-controller/package.json b/packages/accounts-controller/package.json
@@ -56,7 +56,7 @@
     "@metamask/keyring-internal-api": "^9.0.0",
     "@metamask/keyring-utils": "^3.1.0",
     "@metamask/messenger": "^0.3.0",
-    "@metamask/network-controller": "^26.0.0",
+    "@metamask/network-controller": "^27.0.0",
     "@metamask/snaps-controllers": "^14.0.1",
     "@metamask/snaps-sdk": "^9.0.0",
     "@metamask/snaps-utils": "^11.0.0",
diff --git a/packages/assets-controllers/CHANGELOG.md b/packages/assets-controllers/CHANGELOG.md
@@ -9,6 +9,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Changed
 
+- Bump `@metamask/network-controller` from `^26.0.0` to `^27.0.0` ([#7258](https://github.com/MetaMask/core/pull/7258))
 - Bump `@metamask/transaction-controller` from `^62.3.0` to `^62.3.1` ([#7257](https://github.com/MetaMask/core/pull/7257))
 
 ## [92.0.0]
diff --git a/packages/assets-controllers/package.json b/packages/assets-controllers/package.json
@@ -68,7 +68,7 @@
     "@metamask/messenger": "^0.3.0",
     "@metamask/metamask-eth-abis": "^3.1.1",
     "@metamask/multichain-account-service": "^4.0.0",
-    "@metamask/network-controller": "^26.0.0",
+    "@metamask/network-controller": "^27.0.0",
     "@metamask/permission-controller": "^12.1.1",
     "@metamask/phishing-controller": "^16.1.0",
     "@metamask/polling-controller": "^16.0.0",
diff --git a/packages/bridge-controller/CHANGELOG.md b/packages/bridge-controller/CHANGELOG.md
@@ -9,6 +9,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Changed
 
+- Bump `@metamask/network-controller` from `^26.0.0` to `^27.0.0` ([#7258](https://github.com/MetaMask/core/pull/7258))
 - Bump `@metamask/transaction-controller` from `^62.3.0` to `^62.3.1` ([#7257](https://github.com/MetaMask/core/pull/7257))
 - Bump `@metamask/assets-controllers` from `^91.0.0` to `^92.0.0` ([#7253](https://github.com/MetaMask/core/pull/7253))
 
diff --git a/packages/bridge-controller/package.json b/packages/bridge-controller/package.json
@@ -62,7 +62,7 @@
     "@metamask/messenger": "^0.3.0",
     "@metamask/metamask-eth-abis": "^3.1.1",
     "@metamask/multichain-network-controller": "^3.0.0",
-    "@metamask/network-controller": "^26.0.0",
+    "@metamask/network-controller": "^27.0.0",
     "@metamask/polling-controller": "^16.0.0",
     "@metamask/remote-feature-flag-controller": "^2.0.1",
     "@metamask/snaps-controllers": "^14.0.1",
diff --git a/packages/bridge-status-controller/CHANGELOG.md b/packages/bridge-status-controller/CHANGELOG.md
@@ -9,6 +9,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Changed
 
+- Bump `@metamask/network-controller` from `^26.0.0` to `^27.0.0` ([#7258](https://github.com/MetaMask/core/pull/7258))
 - Bump `@metamask/transaction-controller` from `^62.3.0` to `^62.3.1` ([#7257](https://github.com/MetaMask/core/pull/7257))
 
 ## [63.1.0]
diff --git a/packages/bridge-status-controller/package.json b/packages/bridge-status-controller/package.json
@@ -53,7 +53,7 @@
     "@metamask/bridge-controller": "^63.2.0",
     "@metamask/controller-utils": "^11.16.0",
     "@metamask/gas-fee-controller": "^26.0.0",
-    "@metamask/network-controller": "^26.0.0",
+    "@metamask/network-controller": "^27.0.0",
     "@metamask/polling-controller": "^16.0.0",
     "@metamask/snaps-controllers": "^14.0.1",
     "@metamask/superstruct": "^3.1.0",
diff --git a/packages/chain-agnostic-permission/CHANGELOG.md b/packages/chain-agnostic-permission/CHANGELOG.md
@@ -9,7 +9,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Changed
 
-- Bump `@metamask/network-controller` from `^25.0.0` to `^26.0.0` ([#7202](https://github.com/MetaMask/core/pull/7202))
+- Bump `@metamask/network-controller` from `^26.0.0` to `^27.0.0` ([#7202](https://github.com/MetaMask/core/pull/7202), [#7258](https://github.com/MetaMask/core/pull/7258))
 - Bump `@metamask/controller-utils` from `^11.15.0` to `^11.16.0` ([#7202](https://github.com/MetaMask/core/pull/7202))
 - Bump `@metamask/permission-controller` from `^12.1.0` to `^12.1.1` ([#6988](https://github.com/MetaMask/core/pull/6988), [#7202](https://github.com/MetaMask/core/pull/7202))
 
diff --git a/packages/chain-agnostic-permission/package.json b/packages/chain-agnostic-permission/package.json
@@ -50,7 +50,7 @@
   "dependencies": {
     "@metamask/api-specs": "^0.14.0",
     "@metamask/controller-utils": "^11.16.0",
-    "@metamask/network-controller": "^26.0.0",
+    "@metamask/network-controller": "^27.0.0",
     "@metamask/permission-controller": "^12.1.1",
     "@metamask/rpc-errors": "^7.0.2",
     "@metamask/utils": "^11.8.1",
diff --git a/packages/earn-controller/CHANGELOG.md b/packages/earn-controller/CHANGELOG.md
@@ -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), [#7258](https://github.com/MetaMask/core/pull/7258))
   - The dependencies moved are:
     - `@metamask/account-tree-controller` (^4.0.0)
-    - `@metamask/network-controller` (^26.0.0)
+    - `@metamask/network-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.
diff --git a/packages/earn-controller/package.json b/packages/earn-controller/package.json
@@ -55,7 +55,7 @@
     "@metamask/controller-utils": "^11.16.0",
     "@metamask/keyring-api": "^21.0.0",
     "@metamask/messenger": "^0.3.0",
-    "@metamask/network-controller": "^26.0.0",
+    "@metamask/network-controller": "^27.0.0",
     "@metamask/stake-sdk": "^3.2.1",
     "reselect": "^5.1.1"
   },
diff --git a/packages/ens-controller/CHANGELOG.md b/packages/ens-controller/CHANGELOG.md
@@ -9,9 +9,9 @@ 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), [#7258](https://github.com/MetaMask/core/pull/7258))
   - The dependencies moved are:
-    - `@metamask/network-controller` (^26.0.0)
+    - `@metamask/network-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.
diff --git a/packages/ens-controller/package.json b/packages/ens-controller/package.json
@@ -52,7 +52,7 @@
     "@metamask/base-controller": "^9.0.0",
     "@metamask/controller-utils": "^11.16.0",
     "@metamask/messenger": "^0.3.0",
-    "@metamask/network-controller": "^26.0.0",
+    "@metamask/network-controller": "^27.0.0",
     "@metamask/utils": "^11.8.1",
     "punycode": "^2.1.1"
   },
diff --git a/packages/eth-json-rpc-middleware/package.json b/packages/eth-json-rpc-middleware/package.json
@@ -70,7 +70,7 @@
   "devDependencies": {
     "@metamask/auto-changelog": "^3.4.4",
     "@metamask/error-reporting-service": "^3.0.0",
-    "@metamask/network-controller": "^26.0.0",
+    "@metamask/network-controller": "^27.0.0",
     "@ts-bridge/cli": "^0.6.4",
     "@types/deep-freeze-strict": "^1.1.0",
     "@types/jest": "^27.4.1",
diff --git a/packages/gas-fee-controller/CHANGELOG.md b/packages/gas-fee-controller/CHANGELOG.md
@@ -9,9 +9,9 @@ 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), [#7258](https://github.com/MetaMask/core/pull/7258))
   - The dependencies moved are:
-    - `@metamask/network-controller` (^26.0.0)
+    - `@metamask/network-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.
diff --git a/packages/gas-fee-controller/package.json b/packages/gas-fee-controller/package.json
@@ -52,7 +52,7 @@
     "@metamask/controller-utils": "^11.16.0",
     "@metamask/eth-query": "^4.0.0",
     "@metamask/ethjs-unit": "^0.3.0",
-    "@metamask/network-controller": "^26.0.0",
+    "@metamask/network-controller": "^27.0.0",
     "@metamask/polling-controller": "^16.0.0",
     "@metamask/utils": "^11.8.1",
     "@types/bn.js": "^5.1.5",
diff --git a/packages/multichain-api-middleware/CHANGELOG.md b/packages/multichain-api-middleware/CHANGELOG.md
@@ -10,7 +10,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Changed
 
 - Bump `@metamask/permission-controller` from `^12.1.0` to `^12.1.1` ([#7202](https://github.com/MetaMask/core/pull/7202))
-- Bump `@metamask/network-controller` from `^25.0.0` to `^26.0.0` ([#7202](https://github.com/MetaMask/core/pull/7202))
+- Bump `@metamask/network-controller` from `^26.0.0` to `^27.0.0` ([#7202](https://github.com/MetaMask/core/pull/7202), [#7258](https://github.com/MetaMask/core/pull/7258))
 - Bump `@metamask/json-rpc-engine` from `^10.1.1` to `^10.2.0` ([#7202](https://github.com/MetaMask/core/pull/7202))
 - Bump `@metamask/controller-utils` from `^11.15.0` to `^11.16.0` ([#7202](https://github.com/MetaMask/core/pull/7202))
 
diff --git a/packages/multichain-api-middleware/package.json b/packages/multichain-api-middleware/package.json
@@ -52,7 +52,7 @@
     "@metamask/chain-agnostic-permission": "^1.2.2",
     "@metamask/controller-utils": "^11.16.0",
     "@metamask/json-rpc-engine": "^10.2.0",
-    "@metamask/network-controller": "^26.0.0",
+    "@metamask/network-controller": "^27.0.0",
     "@metamask/permission-controller": "^12.1.1",
     "@metamask/rpc-errors": "^7.0.2",
     "@metamask/utils": "^11.8.1",
diff --git a/packages/multichain-network-controller/CHANGELOG.md b/packages/multichain-network-controller/CHANGELOG.md
@@ -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), [#7258](https://github.com/MetaMask/core/pull/7258))
   - The dependencies moved are:
     - `@metamask/accounts-controller` (^35.0.0)
-    - `@metamask/network-controller` (^26.0.0)
+    - `@metamask/network-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.
diff --git a/packages/multichain-network-controller/package.json b/packages/multichain-network-controller/package.json
@@ -54,7 +54,7 @@
     "@metamask/keyring-api": "^21.0.0",
     "@metamask/keyring-internal-api": "^9.0.0",
     "@metamask/messenger": "^0.3.0",
-    "@metamask/network-controller": "^26.0.0",
+    "@metamask/network-controller": "^27.0.0",
     "@metamask/superstruct": "^3.1.0",
     "@metamask/utils": "^11.8.1",
     "@solana/addresses": "^2.0.0",
diff --git a/packages/network-controller/CHANGELOG.md b/packages/network-controller/CHANGELOG.md
@@ -7,6 +7,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [27.0.0]
+
 ### Added
 
 - Add `NetworkController:rpcEndpointChainAvailable` messenger event ([#7166](https://github.com/MetaMask/core/pull/7166))
@@ -1043,7 +1045,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/network-controller@26.0.0...HEAD
+[Unreleased]: https://github.com/MetaMask/core/compare/@metamask/network-controller@27.0.0...HEAD
+[27.0.0]: https://github.com/MetaMask/core/compare/@metamask/network-controller@26.0.0...@metamask/network-controller@27.0.0
 [26.0.0]: https://github.com/MetaMask/core/compare/@metamask/network-controller@25.0.0...@metamask/network-controller@26.0.0
 [25.0.0]: https://github.com/MetaMask/core/compare/@metamask/network-controller@24.3.1...@metamask/network-controller@25.0.0
 [24.3.1]: https://github.com/MetaMask/core/compare/@metamask/network-controller@24.3.0...@metamask/network-controller@24.3.1
diff --git a/packages/network-controller/package.json b/packages/network-controller/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@metamask/network-controller",
-  "version": "26.0.0",
+  "version": "27.0.0",
   "description": "Provides an interface to the currently selected network via a MetaMask-compatible provider object",
   "keywords": [
     "MetaMask",
diff --git a/packages/network-enablement-controller/CHANGELOG.md b/packages/network-enablement-controller/CHANGELOG.md
@@ -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), [#7220](https://github.com/MetaMask/core/pull/7220), [#7236](https://github.com/MetaMask/core/pull/7236), [#7257](https://github.com/MetaMask/core/pull/7257))
+- 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), [#7236](https://github.com/MetaMask/core/pull/7236), [#7257](https://github.com/MetaMask/core/pull/7257), [#7258](https://github.com/MetaMask/core/pull/7258))
   - The dependencies moved are:
     - `@metamask/multichain-network-controller` (^3.0.0)
-    - `@metamask/network-controller` (^26.0.0)
+    - `@metamask/network-controller` (^27.0.0)
     - `@metamask/transaction-controller` (^62.3.1)
   - 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.
diff --git a/packages/network-enablement-controller/package.json b/packages/network-enablement-controller/package.json
@@ -53,7 +53,7 @@
     "@metamask/keyring-api": "^21.0.0",
     "@metamask/messenger": "^0.3.0",
     "@metamask/multichain-network-controller": "^3.0.0",
-    "@metamask/network-controller": "^26.0.0",
+    "@metamask/network-controller": "^27.0.0",
     "@metamask/transaction-controller": "^62.3.1",
     "@metamask/utils": "^11.8.1",
     "reselect": "^5.1.1"
diff --git a/packages/polling-controller/CHANGELOG.md b/packages/polling-controller/CHANGELOG.md
@@ -9,9 +9,9 @@ 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), [#7258](https://github.com/MetaMask/core/pull/7258))
   - The dependencies moved are:
-    - `@metamask/network-controller` (^26.0.0)
+    - `@metamask/network-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.
diff --git a/packages/polling-controller/package.json b/packages/polling-controller/package.json
@@ -50,7 +50,7 @@
   "dependencies": {
     "@metamask/base-controller": "^9.0.0",
     "@metamask/controller-utils": "^11.16.0",
-    "@metamask/network-controller": "^26.0.0",
+    "@metamask/network-controller": "^27.0.0",
     "@metamask/utils": "^11.8.1",
     "@types/uuid": "^8.3.0",
     "fast-json-stable-stringify": "^2.1.0",
diff --git a/packages/sample-controllers/CHANGELOG.md b/packages/sample-controllers/CHANGELOG.md
@@ -9,9 +9,9 @@ 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), [#7258](https://github.com/MetaMask/core/pull/7258))
   - The dependencies moved are:
-    - `@metamask/network-controller` (^26.0.0)
+    - `@metamask/network-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.
diff --git a/packages/sample-controllers/package.json b/packages/sample-controllers/package.json
@@ -50,7 +50,7 @@
   "dependencies": {
     "@metamask/base-controller": "^9.0.0",
     "@metamask/messenger": "^0.3.0",
-    "@metamask/network-controller": "^26.0.0",
+    "@metamask/network-controller": "^27.0.0",
     "@metamask/utils": "^11.8.1"
   },
   "devDependencies": {
diff --git a/packages/selected-network-controller/CHANGELOG.md b/packages/selected-network-controller/CHANGELOG.md
@@ -9,9 +9,9 @@ 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), [#7258](https://github.com/MetaMask/core/pull/7258))
   - The dependencies moved are:
-    - `@metamask/network-controller` (^26.0.0)
+    - `@metamask/network-controller` (^27.0.0)
     - `@metamask/permission-controller` (^12.1.1)
   - 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.
diff --git a/packages/selected-network-controller/package.json b/packages/selected-network-controller/package.json
@@ -51,7 +51,7 @@
     "@metamask/base-controller": "^9.0.0",
     "@metamask/json-rpc-engine": "^10.2.0",
     "@metamask/messenger": "^0.3.0",
-    "@metamask/network-controller": "^26.0.0",
+    "@metamask/network-controller": "^27.0.0",
     "@metamask/permission-controller": "^12.1.1",
     "@metamask/swappable-obj-proxy": "^2.3.0",
     "@metamask/utils": "^11.8.1"
diff --git a/packages/signature-controller/CHANGELOG.md b/packages/signature-controller/CHANGELOG.md
diff --git a/packages/signature-controller/package.json b/packages/signature-controller/package.json
diff --git a/packages/transaction-controller/CHANGELOG.md b/packages/transaction-controller/CHANGELOG.md
diff --git a/packages/transaction-controller/package.json b/packages/transaction-controller/package.json
diff --git a/packages/transaction-pay-controller/CHANGELOG.md b/packages/transaction-pay-controller/CHANGELOG.md
diff --git a/packages/transaction-pay-controller/package.json b/packages/transaction-pay-controller/package.json
diff --git a/packages/user-operation-controller/CHANGELOG.md b/packages/user-operation-controller/CHANGELOG.md
diff --git a/packages/user-operation-controller/package.json b/packages/user-operation-controller/package.json
diff --git a/yarn.lock b/yarn.lock
