749.0.0

@metamask/ramps-controller 3.0.0

Added

• Add getTokens() method to RampsController for fetching available tokens by region and action (#7607)

Changed

• BREAKING: Rename geolocation to userRegion and updateGeolocation() to updateUserRegion() in RampsController (#7563)

• Bump @metamask/controller-utils from ^11.17.0 to ^11.18.0 (#7583)

748.0.0

@metamask/accounts-controller 35.0.1

Changed

• Bump @metamask/snaps-controllers from ^14.0.1 to ^17.2.0 (#7550)
• Bump @metamask/snaps-sdk from ^9.0.0 to ^10.3.0 (#7550)
• Bump @metamask/snaps-utils from ^11.0.0 to ^11.7.0 (#7550)
• Upgrade @metamask/utils from ^11.8.1 to ^11.9.0 (#7511)
• Move peer dependencies for controller and service packages to direct dependencies (#7209, #7258, #7534, #7583, #7604)
  • The dependencies moved are:
    • @metamask/keyring-controller (^25.0.0)
    • @metamask/network-controller (^28.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.
  • 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.

@metamask/bridge-controller 64.4.1

Changed

• Bump @metamask/transaction-controller from ^62.8.0 to ^62.9.1 (#7602, #7604)
• Bump @metamask/assets-controllers from ^95.0.0 to ^95.1.0 (#7600)
• Bump @metamask/network-controller from ^27.2.0 to ^28.0.0 (#7604)
• Bump @metamask/accounts-controller from ^35.0.0 to ^35.0.1 (#7604)
• Bump @metamask/gas-fee-controller from ^26.0.0 to ^26.0.1 (#7604)
• Bump @metamask/multichain-network-controller from ^3.0.0 to ^3.0.1 (#7604)

@metamask/bridge-status-controller 64.4.2

Changed

• Bump @metamask/transaction-controller from ^62.8.0 to ^62.9.1 (#7602, #7604)
• Bump @metamask/network-controller from ^27.2.0 to ^28.0.0 (#7604)
• Bump @metamask/accounts-controller from ^35.0.0 to ^35.0.1 (#7604)
• Bump @metamask/bridge-controller from ^64.4.0 to ^64.4.1 (#7604)
• Bump @metamask/gas-fee-controller from ^26.0.0 to ^26.0.1 (#7604)
• Bump @metamask/polling-controller from ^16.0.0 to ^16.0.1 (#7604)

@metamask/ens-controller 19.0.1

Changed

• Upgrade @metamask/utils from ^11.8.1 to ^11.9.0 (#7511)
• Move peer dependencies for controller and service packages to direct dependencies (#7209, #7258, #7534, #7583, #7604)
  • The dependencies moved are:
    • @metamask/network-controller (^28.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/controller-utils from ^11.16.0 to ^11.18.0 (#7534, #7583)

@metamask/gas-fee-controller 26.0.1

Changed

• Upgrade @metamask/utils from ^11.8.1 to ^11.9.0 (#7511)
• Move peer dependencies for controller and service packages to direct dependencies (#7209, #7258, #7534, #7583, #7604)
  • The dependencies moved are:
    • @metamask/network-controller (^28.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/controller-utils from ^11.16.0 to ^11.18.0 (#7534, #7583)
• Bump @metamask/polling-controller from ^16.0.0 to ^16.0.1 (#7604)

@metamask/multichain-network-controller 3.0.1

Changed

• Upgrade @metamask/utils from ^11.8.1 to ^11.9.0 (#7511)
• Move peer dependencies for controller and service packages to direct dependencies (#7209, #7258, #7534, #7583, #7604)
  • The dependencies moved are:
    • @metamask/accounts-controller (^35.0.1)
    • @metamask/network-controller (^28.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/controller-utils from ^11.16.0 to ^11.18.0 (#7534, #7583)

@metamask/network-controller 28.0.0

Changed

• Corrects the previous 27.2.0 release to document breaking changes that were missed:
  • BREAKING: Remove dependency on @metamask/error-reporting-service (#7542)
    • ErrorReportingService:captureException is no longer an allowed action on the NetworkController messenger. You do not need to delegate its ErrorReportingService:captureException action to the NetworkController messenger.

@metamask/polling-controller 16.0.1

Changed

• Upgrade @metamask/utils from ^11.8.1 to ^11.9.0 (#7511)
• Move peer dependencies for controller and service packages to direct dependencies (#7209, #7258, #7534, #7583, #7604)
  • The dependencies moved are:
    • @metamask/network-controller (^28.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/controller-utils from ^11.16.0 to ^11.18.0 (#7534, #7583)

@metamask/sample-controllers 4.0.1

Changed

• Upgrade @metamask/utils from ^11.8.1 to ^11.9.0 (#7511)
• Move peer dependencies for controller and service packages to direct dependencies (#7209, #7258, #7534, #7583, #7604)
  • The dependencies moved are:
    • @metamask/network-controller (^28.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 "w...

747.0.0

@metamask/transaction-controller 62.9.0

Added

• Add optional targetFiat property to MetamaskPayMetadata type (#7562)

@metamask/transaction-pay-controller 11.0.0

Added

• BREAKING: Support max amount quotes (#7562)
  • Add TransactionPayController:setIsMaxAmount messenger action.
  • Add isMaxAmount property to TransactionData type.
  • Add targetAmount property to TransactionPayQuote and TransactionPayTotals.
  • Update Relay quote requests to use EXACT_INPUT trade type when max amount is selected.
  • Update totals calculation to account for max amount selection.

Changed

• Bump @metamask/controller-utils from ^11.17.0 to ^11.18.0 (#7583)
• Bump @metamask/network-controller from ^27.1.0 to ^27.2.0 (#7583)
• Bump @metamask/assets-controllers from ^94.0.0 to ^95.1.0 (#7584, #7600)
• Bump @metamask/transaction-controller from ^62.7.0 to ^62.9.0 (#7596, #7602)
• Bump @metamask/bridge-controller from ^64.3.0 to ^64.4.0 (#7596)
• Bump @metamask/bridge-status-controller from ^64.3.0 to ^64.4.1 (#7596, #7597)

746.0.0

@metamask/assets-controllers 95.1.0

Added

• Add RWA (Real World Assets) data support for token metadata endpoint (#7595)
  • Update token service to include RWA data in API requests by appending includeRwaData=true parameter to token list API calls
  • TokenListController now includes rwaData optional field in TokenListToken type to support RWA data in token list retrieval
  • Reduced TokenListController cache time from 24hrs to 4hrs.

Changed

• Bump @metamask/multichain-account-service from ^4.1.0 to ^5.0.0 (#7594)
• Bump @metamask/transaction-controller from ^62.7.0 to ^62.8.0 (#7596)
• AccountTrackerController now triggers an immediate balance refresh when the keyring is unlocked, instead of waiting for the next polling cycle (#7585)

Fixed

• Add missing native coin non-zero address for networks: Gnosis and MSU (#7592)

745.0.0

@metamask/bridge-status-controller 64.4.1

Fixed

• Use BRIDGE_PREFERRED_GAS_ESTIMATE from @metamask/bridge-controller for gas price estimates to align with validation (#7582)

744.0.0

@metamask/bridge-controller 64.4.0

Added

• Add intent based transaction support (#6547)

Changed

• Bump @metamask/transaction-controller from ^62.7.0 to ^62.8.0 (#7596)
• Bump @metamask/controller-utils from ^11.17.0 to ^11.18.0 (#7583)
• Bump @metamask/network-controller from ^27.1.0 to ^27.2.0 (#7583)
• Bump @metamask/assets-controllers from ^94.0.0 to ^95.0.0 (#7584)

@metamask/bridge-status-controller 64.4.0

Added

• Add intent based transaction support (#6547)

Changed

• Bump @metamask/transaction-controller from ^62.7.0 to ^62.8.0 (#7596)
• Bump @metamask/bridge-controller from ^64.3.0 to ^64.4.0 (#7596)
• Bump @metamask/controller-utils from ^11.17.0 to ^11.18.0 (#7583)
• Bump @metamask/network-controller from ^27.1.0 to ^27.2.0 (#7583)

@metamask/transaction-controller 62.8.0

Added

• Add optional isStateOnly property to TransactionMeta and AddTransactionOptions (#7591)
  • Transactions with isStateOnly set to true have no lifecycle and are not signed or published.
  • Transactions are also excluded from confirmation polling.

Changed

• Bump @metamask/remote-feature-flag-controller from ^3.1.0 to ^4.0.0 (#7546)
• Upgrade @metamask/utils from ^11.8.1 to ^11.9.0 (#7511)
• Update transaction timeout to check time since submission or when transaction was last seen on network (#7464)
  • Uses blockTime from acceleratedPolling feature flag.
• Deprecate history and sendFlowHistory properties from TransactionMeta and TransactionController options (#7326)
• Bump @metamask/remote-feature-flag-controller from ^3.0.0 to ^3.1.0 (#7519)
• Bump @metamask/network-controller from ^27.0.0 to ^27.2.0 (#7534, #7583)
• Bump @metamask/controller-utils from ^11.16.0 to ^11.18.0 (#7534, #7583)
• Update error message for failed on-chain transactions in PendingTransactionTracker (#7552)

Fixed

• Include pending authorizations in nonce calculation (#7446)

743.0.0

@metamask/multichain-account-service 5.0.0

Added

• Wait for Snap platform to be ready before any wallet/group operations (#7266)
• Add SnapAccountProvider.withSnap protected helper (#7266)
  • This is used to protect any Snap operation behind a guard that checks if the Snap platform is ready.
• Add MultichainAccountService:ensureCanUseSnapPlatform method and action.
  • This will resolve once the Snap platform is ready for the first time and will throw afterward if Snap platform has been disabled dynamically.
  • This action is mostly used internally by any Snap-based account providers.

Changed

• BREAKING: The SnapAccountProvider.client property is now private (#7266)
  • You now need to use SnapAccountProvider.withSnap to access to it.
• Bump @metamask/snaps-controllers from ^14.0.1 to ^17.2.0 (#7550)
• Bump @metamask/snaps-sdk from ^9.0.0 to ^10.3.0 (#7550)
• Bump @metamask/snaps-utils from ^11.0.0 to ^11.7.0 (#7550)
• Upgrade @metamask/utils from ^11.8.1 to ^11.9.0 (#7511)
• Remove dependency on @metamask/error-reporting-service (#7542)
  • The service no longer needs ErrorReportingService:captureException.

742.0.0

@metamask/assets-controllers 95.0.0

Added

• Add RWA (Real World Assets) data support to token service (#7560)
  • Add includeRwaData optional parameter to getTrendingTokens function to include RWA data in results
  • Add TokenRwaData type for RWA token metadata (market hours, pause times, ticker, instrument type)
  • Add TokenSearchItem type with optional rwaData field for token search results
  • Add rwaData optional field to TrendingAsset type
• Update spot-prices endpoint list of supported chains and assets (#7543)
• Export selectAllAssets (#7496)
• Add multicall address for MSU (MapleStory Universe) (#7453)
• Add MSU (MapleStory Universe) and Etherlink in Spot Prices support (#7453)
• Set MSU native token address to eip155:68414/erc20:0xf2b51cc1850fed939658317a22d73d3482767591 instead of eip155:68414/erc20:0x0000000000000000000000000000000000000000 - particular case where the native token doesn't have the zero address (#7578)

Changed

• Bump @metamask/snaps-controllers from ^14.0.1 to ^17.2.0 (#7550)
• Bump @metamask/snaps-sdk from ^9.0.0 to ^10.3.0 (#7550)
• Bump @metamask/snaps-utils from ^11.0.0 to ^11.7.0 (#7550)
• Upgrade @metamask/utils from ^11.8.1 to ^11.9.0 (#7511)
• Bump @metamask/permission-controller from ^12.1.1 to ^12.2.0 (#7559)
• BREAKING: AccountTrackerController now requires KeyringController:getState action and KeyringController:lock event in addition to existing allowed actions and events (#7492)
  • Added #isLocked property to track keyring lock state, initialized from KeyringController:getState
  • Added isActive getter that returns true when keyring is unlocked and user is onboarded
  • Balance updates are now skipped when controller is not active (locked or not onboarded)
  • KeyringController:unlock event now only updates lock state without triggering immediate refresh
  • KeyringController:lock event sets controller to inactive state
• AccountTrackerController now only refreshes balances for the newly added network on NetworkController:networkAdded event instead of all networks (#7492)
• Bump @metamask/transaction-controller from ^62.5.0 to ^62.7.0 (#7494)
• Bump @metamask/multichain-account-service from ^4.0.1 to ^4.1.0 (#7515
• Bump @metamask/controller-utils from ^11.16.0 to ^11.18.0 (#7534, #7583)
• Bump @metamask/network-controller from ^27.0.0 to ^27.2.0 (#7534, #7583)

741.0.0

@metamask/controller-utils 11.18.0

Changed

• Upgrade @metamask/utils from ^11.8.1 to ^11.9.0 (#7511)
• Update MegaETH Testnet "v2" RPC constants (#7566)
  • Change RPC endpoint from https://timothy.megaeth.com/rpc to https://carrot.megaeth.com/rpc

@metamask/network-controller 27.2.0

Changed

• Upgrade @metamask/utils from ^11.8.1 to ^11.9.0 (#7511)
• Remove dependency on @metamask/error-reporting-service (#7542)
  • The service no longer needs ErrorReportingService:captureException.
• Bump @metamask/controller-utils from ^11.17.0 to ^11.18.0 (#7583)

740.0.0

@metamask/ramps-controller 2.1.0

Added

• Add eligibility state (#7539)

• Add createRequestSelector utility function for creating memoized selectors for RampsController request states (#7554)

• Add request caching infrastructure with TTL, deduplication, and abort support (#7536)

Changed

• Bump @metamask/controller-utils from ^11.16.0 to ^11.17.0 (#7534)