262.0.0

@metamask/accounts-controller 20.0.1

Fixed

• Make implicit peer dependencies explicit (#4974)
  • Add the following packages as peer dependencies of this package to satisfy peer dependency requirements from other dependencies:
    • @metamask/providers ^18.1.0 (required by @metamask/keyring-api)
    • webextension-polyfill ^0.10.0 || ^0.11.0 || ^0.12.0 (required by @metamask/providers)
  • These dependencies really should be present in projects that consume this package (e.g. MetaMask clients), and this change ensures that they now are.
  • Furthermore, we are assuming that clients already use these dependencies, since otherwise it would be impossible to consume this package in its entirety or even create a working build. Hence, the addition of these peer dependencies is really a formality and should not be breaking.
• Correct ESM-compatible build so that imports of the following packages that re-export other modules via export * are no longer corrupted: (#5011)
  • @metamask/keyring-api
  • @metamask/eth-snap-keyring

@metamask/address-book-controller 6.0.2

Changed

• Bump @metamask/utils from ^9.1.0 to ^10.0.0 (#4831)
• Bump @metamask/base-controller from ^7.0.1 to ^7.0.2 (#4862)
• Bump @metamask/controller-utils from ^11.3.0 to ^11.4.4 (#4834, #4862, #4870, #4915, #5012)

@metamask/announcement-controller 7.0.2

Changed

• Bump @metamask/base-controller from ^7.0.1 to ^7.0.2 (#4862)

@metamask/assets-controllers 45.1.1

Changed

• Bump @metamask/controller-utils from ^11.3.0 to ^11.4.4 (#5012)
• Bump @metamask/polling-controller from ^12.0.1 to ^12.0.2 (#5012)

Fixed

• Make implicit peer dependencies explicit (#4974)
  • Add the following packages as peer dependencies of this package to satisfy peer dependency requirements from other dependencies:
    • @metamask/providers ^18.1.0 (required by @metamask/keyring-api)
    • webextension-polyfill ^0.10.0 || ^0.11.0 || ^0.12.0 (required by @metamask/providers)
  • These dependencies really should be present in projects that consume this package (e.g. MetaMask clients), and this change ensures that they now are.
  • Furthermore, we are assuming that clients already use these dependencies, since otherwise it would be impossible to consume this package in its entirety or even create a working build. Hence, the addition of these peer dependencies is really a formality and should not be breaking.
• Fix TokensController.ignoreTokens so that if a network is provided, allIgnoredTokens, allTokens, and allDetectedTokens for that network no longer get corrupted with tokens from the globally selected network (#4967)
• Correct ESM-compatible build so that imports of the following packages that re-export other modules via export * are no longer corrupted: (#5011)
  • @metamask/abi-utils
  • @metamask/contract-metadata
  • @metamask/eth-query
  • @ethereumjs/util
  • bn.js
  • cockatiel
  • lodash
  • single-call-balance-checker-abi

@metamask/build-utils 3.0.2

Changed

• Bump @metamask/utils from ^9.1.0 to ^10.0.0 (#4831)

@metamask/chain-controller 0.2.1

Fixed

• Make implicit peer dependencies explicit (#4974)
  • Add the following packages as peer dependencies of this package to satisfy peer dependency requirements from other dependencies:
    • @metamask/providers ^18.1.0 (required by @metamask/keyring-api)
    • webextension-polyfill ^0.10.0 || ^0.11.0 || ^0.12.0 (required by @metamask/providers)
  • These dependencies really should be present in projects that consume this package (e.g. MetaMask clients), and this change ensures that they now are.
  • Furthermore, we are assuming that clients already use these dependencies, since otherwise it would be impossible to consume this package in its entirety or even create a working build. Hence, the addition of these peer dependencies is really a formality and should not be breaking.

@metamask/controller-utils 11.4.4

Fixed

• Make implicit peer dependencies explicit (#4974)
  • Add the following packages as peer dependencies of this package to satisfy peer dependency requirements from other dependencies:
    • @babel/runtime@^7.0.0 (required by @metamask/ethjs-unit)
  • These dependencies really should be present in projects that consume this package (e.g. MetaMask clients), and this change ensures that they now are.
  • Furthermore, we are assuming that clients already use these dependencies, since otherwise it would be impossible to consume this package in its entirety or even create a working build. Hence, the addition of these peer dependencies is really a formality and should not be breaking.
• Correct ESM-compatible build so that imports of the following packages that re-export other modules via export * are no longer corrupted: (#5011)
  • bn.js
  • eth-ens-namehash
  • fast-deep-equal

@metamask/ens-controller 15.0.1

Changed

• Bump @metamask/base-controller from ^7.0.1 to ^7.0.2 (#4862)
• Bump @metamask/controller-utils from ^11.4.0 to ^11.4.4 (#4862, #4870, #4915, #5012)

Fixed

• Correct ESM-compatible build so that imports of the following packages that re-export other modules via export * are no longer corrupted: (#5011)
  • punycode/punycode.js

@metamask/gas-fee-controller 22.0.2

Changed

• Bump @metamask/controller-utils from ^11.4.3 to ^11.4.4 (#5012)
• Bump @metamask/polling-controller from ^12.0.1 to ^12.0.2 (#5012)

Fixed

• Make implicit peer dependencies explicit (#4974)
  • Add the following packages as peer dependencies of this package to satisfy peer dependency requirements from other dependencies:
    • @babel/runtime@^7.0.0 (required by @metamask/ethjs-unit)
  • These dependencies really should be present in projects that consume this package (e.g. MetaMask clients), and this change ensures that they now are.
  • Furthermore, we are assuming that clients already use these dependencies, since otherwise it would be impossible to consume this package in its entirety or even create a working build. Hence, the addition of these peer dependencies is really a formality and should not be breaking.
• Correct ESM-compatible build so that imports of the following packages that re-export other modules via export * are no longer corrupted: (#5011)
  • @metamask/eth-query
  • bn.js

@metamask/keyring-controller 19.0.1

Changed

• Bump @metamask/message-manager from ^11.0.1 to ^11.0.2 (#5012)

Fixed

• Make implicit peer dependencies explicit (#4974)
  • Add the following packages as peer dependencies of this package to satisfy peer dependency requirements from other dependencies:
    • @metamask/providers ^18.1.0 (required by @metamask/keyring-api)
    • webextension-polyfill ^0.10.0 || ^0.11.0 || ^0.12.0 (required by @metamask/providers)
  • These dependencies really should be present in projects that consume this package (e.g. MetaMask clients), and this change ensures that they now are.
  • Furthermore, we are assuming that clients already use these dependencies, since otherwise it would be impossible to consume this package in its entirety or even create a working build. Hence, the addition of these peer dependencies is really a formality and should not be breaking.
• Correct ESM-compatible build so that imports of the following packages that re-export other modules via export * are no longer corrupted: (#5011)
  • @metamask/eth-hd-keyring
  • @metamask/eth-simple-keyring
  • @ethereumjs/util
  • ethereumjs-wallet

@metamask/logging-controller 6.0.3

Changed

• Bump @metamask/controller-utils from ^11.4.3 to ^11.4.4 (#5012)

@metamask/message-manager 11.0.2

Changed

• Bump @metamask/controller-utils from ^11.4.2 to ^11.4.4 (#4915, #5012)

@metamask/multichain 1.1.1

Changed

• Bump @metamask/controller-utils from ^11.4.3 to ^11.4.4 (#5012)
• Correct ESM-compatible build so that imports of the following packages that re-export other modules via export * are no longer corrupted: (#5011)
  • @metamask/api-specs
  • lodash

@metamask/name-controller 8.0.2

Changed

• Bump @metamask/controller-utils from ^11.3.0 to ^11.4.4...

261.0.0

@metamask/remote-feature-flag-controller 1.0.0

Added

• Initial release of the RemoteFeatureFlagController. (#4931)
  • This controller manages the retrieval and caching of remote feature flags. It fetches feature flags from a remote API, caches them, and provides methods to access and manage these flags. The controller ensures that feature flags are refreshed based on a specified interval and handles cases where the controller is disabled or the network is unavailable.

260.0.0

@metamask/multichain 1.1.0

Changed

• Revoke the CAIP-25 endowment if the only eip155 account or scope is removed (#4978)

259.0.0

@metamask/transaction-controller 41.0.0

Added

• BREAKING: Remove global network usage (#4920)
  • Add required networkClientId argument to handleMethodData method.

Changed

• BREAKING: Remove global network usage (#4920)
  • Require networkClientId option in addTransaction method.
  • Require networkClientId property in TransactionMeta type.
  • Change wipeTransactions method arguments to optional object containing address and chainId properties.
  • Require networkClientId argument in estimateGas, estimateGasBuffered and getNonceLock methods.

Removed

• BREAKING: Remove global network usage (#4920)
  • Remove the blockTracker, isMultichainEnabled, onNetworkStateChange and provider constructor options.
  • Remove filterToCurrentNetwork option from getTransactions method.

@metamask/user-operation-controller 20.0.0

Changed

• BREAKING: Bump @metamask/transaction-controller peer dependency from ^40.1.0 to ^41.0.0 (#4982)

258.0.0

@metamask/queued-request-controller 8.0.0

Changed

• BREAKING: Bump @metamask/selected-network-controller peer dependency from ^19.0.0 to ^20.0.0 (#4979)
• Bump @metamask/controller-utils from ^11.4.2 to ^11.4.3 (#4915)

Removed

• BREAKING: createQueuedRequestMiddleware no longer takes a useRequestQueue parameter. All requests are now queued if shouldEnqueueRequest(req) returns true. (#4941)

@metamask/selected-network-controller 20.0.0

Changed

• Bump @metamask/base-controller from ^7.0.1 to ^7.0.2 (#4862)
• Bump @metamask/json-rpc-engine from ^10.0.0 to ^10.0.1 (#4862)

Removed

• BREAKING: The SelectedNetworkController constructor no longer expects a useRequestPreference boolean nor an onPreferencesStateChange listener. Removal of these parameters means that domains state will always be added for sites that are granted permissions. (#4941)

257.0.0

@metamask/transaction-controller 40.1.0

Added

• Add firstTimeInteraction to transaction meta (#4895)
  • This is a boolean value that indicates whether the transaction is the first time the user has interacted with it.
• Add isFirstTimeInteractionEnabled callback constructor option (#4895)
  • This is a function that returns a boolean value indicating whether the first time interaction check should be enabled.

256.0.0

@metamask/assets-controllers 45.1.0

Added

• chainIdToNativeTokenAddress to record chains with unique (non-zero) addresses (#4952)
• getNativeTokenAddress() exported function to return the correct native token address for native assets (#4952)
• add support for all added networks when switching account for Token Detection (#4957)

Changed

• Update price API calls to use the native token by chain instead of relying on the zero address. (#4952)
• Update TokenRatesController market data mapping to use getNativeTokenAddress instead of the zero address for native tokens. (#4952)

255.0.0

@metamask/multichain 1.0.0

Added

• Initial release (#4962)

254.0.0

@metamask/accounts-controller 20.0.0

Changed

• BREAKING: Bump peer dependency @metamask/keyring-controller from ^18.0.0 to ^19.0.0 (#4915)
• BREAKING: Bump @metamask/keyring-api from ^8.1.3 to ^10.1.0 (#4948)
  • If you are depending on @metamask/providers directly, you will need to upgrade to 18.1.0.
• Bump @metamask/eth-snap-keyring from ^4.3.6 to ^5.0.1 (#4948)
• Bump @metamask/snaps-utils from ^4.3.6 to ^8.3.0 (#4948)
• Bump @metamask/snaps-sdk from ^6.5.0 to ^6.7.0 (#4948)

@metamask/assets-controllers 45.0.0

Changed

• BREAKING: Bump @metamask/keyring-controller peer dependency from ^18.0.0 to ^19.0.0 (#4195)
• BREAKING: Bump @metamask/accounts-controller peer dependency from ^19.0.0 to ^20.0.0 (#4195)
• BREAKING: Bump @metamask/preferences-controller peer dependency from ^14.0.0 to ^15.0.0 (#4195)

@metamask/chain-controller 0.2.0

Changed

• BREAKING: Bump @metamask/keyring-api from ^8.1.3 to ^10.1.0 (#4948)
  • If you are depending on @metamask/providers directly, you will need to upgrade to 18.1.0.
• Bump @metamask/snaps-utils from ^4.3.6 to ^8.3.0 (#4948)
• Bump @metamask/snaps-sdk from ^6.5.0 to ^6.7.0 (#4948)
• Bump @metamask/snaps-controllers from ^9.7.0to ^9.10.0 (#4948)
• Bump @metamask/utils from ^9.1.0 to ^10.0.0 (#4831)

@metamask/keyring-controller 19.0.0

Changed

• BREAKING: Bump @metamask/keyring-api from ^8.1.3 to ^10.1.0 (#4948)
  • If you are depending on @metamask/providers directly, you will need to upgrade to 18.1.0.

@metamask/notification-services-controller 0.14.0

Changed

• BREAKING: Bump @metamask/keyring-controller peer dependency from ^18.0.0 to ^19.0.0 (#4195)
• BREAKING: Bump @metamask/profile-sync-controller peer dependency from ^1.0.0 to ^2.0.0 (#4195)

@metamask/preferences-controller 15.0.0

Changed

• BREAKING: Bump @metamask/keyring-controller peer dependency from ^18.0.0 to ^19.0.0 (#4195)

@metamask/profile-sync-controller 2.0.0

Changed

• BREAKING: Bump @metamask/keyring-controller peer dependency from ^18.0.0 to ^19.0.0 (#4195)
• BREAKING: Bump @metamask/accounts-controller peer dependency from ^19.0.0 to ^20.0.0 (#4195)

@metamask/signature-controller 23.0.0

Changed

• BREAKING: Bump @metamask/keyring-controller peer dependency from ^18.0.0 to ^19.0.0 (#4195)

@metamask/transaction-controller 40.0.0

Changed

• BREAKING: Bump @metamask/accounts-controller peer dependency from ^19.0.0 to ^20.0.0 (#4195)

@metamask/user-operation-controller 19.0.0

Changed

• BREAKING: Bump @metamask/keyring-controller peer dependency from ^18.0.0 to ^19.0.0 (#4195)
• BREAKING: Bump @metamask/transaction-controller peer dependency from ^39.0.0 to ^40.0.0 (#4195)

253.0.0

@metamask/transaction-controller 39.1.0

Changed

• Temporarily increase the pending transaction polling rate when polling starts (#4917)
  • Poll every 3 seconds up to ten times, then poll on each new block.