Releases: MetaMask/core
Releases · MetaMask/core
754.0.0
@metamask/ramps-controller 4.0.0
Added
-
Add
preferredProviderstate andsetPreferredProvider()method to RampsController (#7617) -
Export
UserRegiontype (#7646) -
Add
defaultAmountandquickAmountsfields to theCountrytype (#7645) -
Add
providersstate andgetProviders()method to RampsController. Providers are automatically fetched on init and when the region changes (#7652)
Changed
-
BREAKING: Change
userRegionfromstring | nulltoUserRegion | null. Access region code viauserRegion.regionCode. (#7646) -
Update
getCountries()endpoint to use v2 API (v2/regions/countries) (#7645) -
Add
getApiPath()helper function for versioned API paths with v2 default (#7645)
Removed
- BREAKING: Remove eligibility concept from RampsController. The
eligibilitystate,updateEligibility()method, andgetEligibility()service method have been removed. TheEligibilitytype andRampsServiceGetEligibilityActionare no longer exported. (#7651)
753.0.0
@metamask/profile-metrics-controller 3.0.0
Added
ProfileMetricsControllercontructor now accepts an optionalinitialDelayDurationparameter (#7624)- The parameter can be used to override the default time-based delay for the first data collection after opt-in
- Add
skipInitialDelay()method toProfileMetricsController(#7624)- The method can be also called through the
ProfileMetricsController:skipInitialDelayaction via messenger
- The method can be also called through the
Changed
- BREAKING:
ProileMetricsControllerMessengernow requires theTransactionController:transactionSubmittedaction to be allowed (#7624) - Set time-based delay for first
ProfileMetricsControllerdata collection after opt-in (#7624) - Upgrade
@metamask/utilsfrom^11.8.1to^11.9.0(#7511) - Bump
@metamask/controller-utilsfrom^11.16.0to^11.18.0(#7534, #7583) - Bump
@metamask/accounts-controllerfrom^35.0.0to^35.0.2(#7604, #7642) - Bump
@metamask/polling-controllerfrom^16.0.0to^16.0.2(#7604, #7642)
752.0.0
@metamask/accounts-controller 35.0.2
Changed
- Bump
@metamask/network-controllerfrom^28.0.0to^29.0.0(#7642)
@metamask/assets-controllers 95.3.0
Added
- Add BOB (0xed88) mapping to eip155:60808/erc20:0x0000000000000000000000000000000000000000 (#7635)
Changed
- Bump
@metamask/accounts-controllerfrom^35.0.1to^35.0.2(#7642) - Bump
@metamask/network-controllerfrom^28.0.0to^29.0.0(#7642) - Bump
@metamask/polling-controllerfrom^16.0.1to^16.0.2(#7642) - Bump
@metamask/transaction-controllerfrom^62.9.1to^62.9.2(#7642)
Fixed
- Fix native token fiat calculation for chains without market data by using currency rate fallback (#7636)
@metamask/bridge-controller 64.5.1
Changed
- Bump
@metamask/accounts-controllerfrom^35.0.1to^35.0.2(#7642) - Bump
@metamask/assets-controllersfrom^95.2.0to^95.3.0(#7642) - Bump
@metamask/gas-fee-controllerfrom^26.0.1to^26.0.2(#7642) - Bump
@metamask/multichain-network-controllerfrom^3.0.1to^3.0.2(#7642) - Bump
@metamask/network-controllerfrom^28.0.0to^29.0.0(#7642) - Bump
@metamask/polling-controllerfrom^16.0.1to^16.0.2(#7642) - Bump
@metamask/transaction-controllerfrom^62.9.1to^62.9.2(#7642)
@metamask/bridge-status-controller 64.4.3
Changed
- Bump
@metamask/accounts-controllerfrom^35.0.1to^35.0.2(#7642) - Bump
@metamask/gas-fee-controllerfrom^26.0.1to^26.0.2(#7642) - Bump
@metamask/network-controllerfrom^28.0.0to^29.0.0(#7642) - Bump
@metamask/polling-controllerfrom^16.0.1to^16.0.2(#7642) - Bump
@metamask/transaction-controllerfrom^62.9.1to^62.9.2(#7642) - Bump
@metamask/bridge-controllerfrom^64.4.1to^64.5.1(#7622, #7642)
@metamask/connectivity-controller 0.1.0
Added
- Initial release (#7623)
@metamask/earn-controller 11.1.0
Added
- Add Tron staking APY support with
tron_stakingstate, methods, and selectors (#7448)
Changed
- Move peer dependencies for controller and service packages to direct dependencies (#7209, #7258, #7534, #7583, #7604, #7642)
- The dependencies moved are:
@metamask/account-tree-controller(^4.0.0)@metamask/network-controller(^29.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-a1.0.0 and@metamask/controller-b1.0.0, and@metamask/controller-bdepends on@metamask/controller-a1.1.0.
- For example, this scenario would be valid: a client relies on
- Note, however, that the versions specified in the client's
package.jsonalways "win", and you are expected to keep them up to date so as not to break controller and service intercommunication.
- The dependencies moved are:
- Bump
@metamask/controller-utilsfrom^11.16.0to^11.18.0(#7534, #7583)
@metamask/ens-controller 19.0.2
Changed
- Bump
@metamask/network-controllerfrom^28.0.0to^29.0.0(#7642)
@metamask/eth-block-tracker 15.0.1
Changed
- Upgrade
@metamask/utilsfrom^11.8.1to^11.9.0(#7511)
@metamask/gas-fee-controller 26.0.2
Changed
- Bump
@metamask/network-controllerfrom^28.0.0to^29.0.0(#7642) - Bump
@metamask/polling-controllerfrom^16.0.1to^16.0.2(#7642)
@metamask/json-rpc-engine 10.2.1
Changed
- Upgrade
@metamask/utilsfrom^11.8.1to^11.9.0(#7511)
Fixed
- Ensure non-object data in RPC errors is deserialized correctly when using JsonRpcEngine compatibility tools (#7638)
@metamask/multichain-api-middleware 1.2.6
Changed
- Bump
@metamask/json-rpc-enginefrom^10.2.0to^10.2.1(#7642) - Upgrade
@metamask/utilsfrom^11.8.1to^11.9.0(#7511) - Bump
@metamask/network-controllerfrom^27.0.0to^29.0.0(#7534, #7583, #7604, #7642) - Bump
@metamask/controller-utilsfrom^11.16.0to^11.18.0(#7534, #7583) - Bump
@metamask/permission-controllerfrom^12.1.1to^12.2.0(#7559) - Bump
@metamask/chain-agnostic-permissionfrom^1.3.0to^1.4.0(#7567)
Fixed
- Fix
wallet_revokeSessionto handle cases whereparamsis not provided (#7551)
@metamask/multichain-network-controller 3.0.2
Changed
- Bump
@metamask/accounts-controllerfrom^35.0.1to^35.0.2(#7642) - Bump
@metamask/network-controllerfrom^28.0.0to^29.0.0(#7642)
@metamask/network-controller 29.0.0
Added
- Add dependency
@metamask/connectivity-controller^0.1.0(#7642)
Changed
- Bump
@metamask/eth-block-trackerfrom^15.0.0to^15.0.1(#7642) - Bump
@metamask/json-rpc-enginefrom^10.2.0to^10.2.1(#7642) - Bump
@metamask/eth-json-rpc-middlewarefrom^22.0.1to^23.0.0(#7634) - BREAKING: NetworkController now requires
ConnectivityController:getStateaction handler to be registered on the messenger (#7627)- The
NetworkControllernow depends on theConnectivityControllerto prevent retries and suppress events when the user is offline. - When offline,
NetworkController:rpcEndpointUnavailableandNetworkController:rpcEndpointDegradedevents are suppressed since retries don't occur and circuit breakers don't trigger. - You must register a
ConnectivityController:getStateaction handler on your root messenger that returns an object with aconnectivityStatusproperty ('online'or'offline'). - You must delegate the
ConnectivityController:getStateaction from your root messenger to theNetworkControllerMessengerusingrootMessenger.delegate({ messenger: networkControllerMessenger, actions: ['ConnectivityController:getState'] }).
- The
@metamask/network-enablement-controller 4.1.0
Added
- Add
nativeAssetIdentifiersstate property that maps CAIP-2 chain IDs to CAIP-19-like native asset identifiers (e.g.,eip155:1/slip44:60) (#7609) - Add
initNativeAssetIdentifiersmethod to populatenativeAssetIdentifiersstate property (#7609)- This is designed to be called during controller initialization.
- Add
Slip44Serviceto look up SLIP-44 coin types by native currency symbol (#7609) - Add
@metamask/slip44dependency for SLIP-44 coin type lookups (#7609) - Subscribe to
NetworkController:stateChangeto updatenativeAssetIdentifierswhen a network's native currency changes (#7609)
Changed
751.0.0
@metamask/eth-json-rpc-middleware 23.0.0
Added
- Support for
wallet_getSupportedExecutionPermissionsandwallet_getGrantedExecutionPermissionsRPC methods (#7603)
Changed
- Upgrade
@metamask/utilsfrom^11.8.1to^11.9.0(#7511) - BREAKING: Changed
wallet_requestExecutionPermissionsto comply with 7715 spec revisions.
@metamask/gator-permissions-controller 1.0.0
Changed
- Bump
@metamask/snaps-controllersfrom^14.0.1to^17.2.0(#7550) - Bump
@metamask/snaps-sdkfrom^9.0.0to^10.3.0(#7550) - Bump
@metamask/snaps-utilsfrom^11.0.0to^11.7.0(#7550) - Upgrade
@metamask/utilsfrom^11.8.1to^11.9.0(#7511) - Bump
@metamask/transaction-controllerfrom^62.5.0to^62.9.1(#7430, #7494, #7596, #7602, #7604) - BREAKING: Gator Permissions Controller and Gator Permission Decoder core types have been updated to comply with 7715 spec revisions (#7613)
- Bump
@metamask/7715-permission-typefrom^0.4.0to^0.5.0
- Bump
@metamask/shield-controller 5.0.0
Changed
- Bump
@metamask/controller-utilsfrom^11.17.0to^11.18.0(#7583) - BREAKING: Bump
@metamask/signature-controllerfrom^38.0.0to^39.0.0(#7604, #7634)- When passing a signature request to
checkSignatureCoverage, thedecodedPermissionproperty of the request has a different shape. See changelog for@metamask/gator-permissions-controller1.0.0 for more.
- When passing a signature request to
- Bump
@metamask/transaction-controllerfrom^62.7.0to^62.9.1(#7596, #7602, #7604)
@metamask/signature-controller 39.0.0
Changed
- Bump
@metamask/gator-permissions-controllerfrom0.8.0to1.0.0(#7634)
750.0.0
@metamask/assets-controllers 95.2.0
Added
- Add RWA data to asset fetching endpoints (#7548)
- Add Rootstock (0x1e) mapping to eip155:30/erc20:0x542fda317318ebf1d3deaf76e0b632741a7e677d for RBTC (#7601)
Changed
- Bump
@metamask/transaction-controllerfrom^62.8.0to^62.9.1(#7602, #7604) - Bump
@metamask/network-controllerfrom^27.2.0to^28.0.0(#7604) - Bump
@metamask/accounts-controllerfrom^35.0.0to^35.0.1(#7604) - Bump
@metamask/polling-controllerfrom^16.0.0to^16.0.1(#7604) - Update Plasma (0x2611) mapping to eip155:9745/erc20:0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee for XPL (#7601)
TokensController.watchAssetnow supports optional origin/page metadata and safely falls back for empty origins to avoid rejected approvals (#7612)- Refactor
CurrencyRateControllerexchange rate fetching with improved fallback logic (#7606)- Improved partial success handling: when some currencies succeed via the Price API and others fail, only failed currencies trigger the fallback mechanism
- Extracted helper methods for better code organization and testability
@metamask/bridge-controller 64.5.0
Added
- Add
has_gas_included_quoteproperty toQuoteFetchDatatype and compute it inQuotesReceivedevent to indicate if any received quote has gas included (#7611) - Add optional
usd_balance_sourceproperty toQuotesReceivedevent andgetQuotesReceivedPropertiesutility to allow clients to pass the source token balance in USD (#7611)
Changed
- Bump
@metamask/assets-controllersfrom^95.1.0to^95.2.0(#7622)
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
748.0.0
@metamask/accounts-controller 35.0.1
Changed
- Bump
@metamask/snaps-controllersfrom^14.0.1to^17.2.0(#7550) - Bump
@metamask/snaps-sdkfrom^9.0.0to^10.3.0(#7550) - Bump
@metamask/snaps-utilsfrom^11.0.0to^11.7.0(#7550) - Upgrade
@metamask/utilsfrom^11.8.1to^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-a1.0.0 and@metamask/controller-b1.0.0, and@metamask/controller-bdepends on@metamask/controller-a1.1.0.
- For example, this scenario would be valid: a client relies on
- Note, however, that the versions specified in the client's
package.jsonalways "win", and you are expected to keep them up to date so as not to break controller and service intercommunication.
- The dependencies moved are:
@metamask/bridge-controller 64.4.1
Changed
- Bump
@metamask/transaction-controllerfrom^62.8.0to^62.9.1(#7602, #7604) - Bump
@metamask/assets-controllersfrom^95.0.0to^95.1.0(#7600) - Bump
@metamask/network-controllerfrom^27.2.0to^28.0.0(#7604) - Bump
@metamask/accounts-controllerfrom^35.0.0to^35.0.1(#7604) - Bump
@metamask/gas-fee-controllerfrom^26.0.0to^26.0.1(#7604) - Bump
@metamask/multichain-network-controllerfrom^3.0.0to^3.0.1(#7604)
@metamask/bridge-status-controller 64.4.2
Changed
- Bump
@metamask/transaction-controllerfrom^62.8.0to^62.9.1(#7602, #7604) - Bump
@metamask/network-controllerfrom^27.2.0to^28.0.0(#7604) - Bump
@metamask/accounts-controllerfrom^35.0.0to^35.0.1(#7604) - Bump
@metamask/bridge-controllerfrom^64.4.0to^64.4.1(#7604) - Bump
@metamask/gas-fee-controllerfrom^26.0.0to^26.0.1(#7604) - Bump
@metamask/polling-controllerfrom^16.0.0to^16.0.1(#7604)
@metamask/ens-controller 19.0.1
Changed
- Upgrade
@metamask/utilsfrom^11.8.1to^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-a1.0.0 and@metamask/controller-b1.0.0, and@metamask/controller-bdepends on@metamask/controller-a1.1.0.
- For example, this scenario would be valid: a client relies on
- Note, however, that the versions specified in the client's
package.jsonalways "win", and you are expected to keep them up to date so as not to break controller and service intercommunication.
- The dependencies moved are:
- Bump
@metamask/controller-utilsfrom^11.16.0to^11.18.0(#7534, #7583)
@metamask/gas-fee-controller 26.0.1
Changed
- Upgrade
@metamask/utilsfrom^11.8.1to^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-a1.0.0 and@metamask/controller-b1.0.0, and@metamask/controller-bdepends on@metamask/controller-a1.1.0.
- For example, this scenario would be valid: a client relies on
- Note, however, that the versions specified in the client's
package.jsonalways "win", and you are expected to keep them up to date so as not to break controller and service intercommunication.
- The dependencies moved are:
- Bump
@metamask/controller-utilsfrom^11.16.0to^11.18.0(#7534, #7583) - Bump
@metamask/polling-controllerfrom^16.0.0to^16.0.1(#7604)
@metamask/multichain-network-controller 3.0.1
Changed
- Upgrade
@metamask/utilsfrom^11.8.1to^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-a1.0.0 and@metamask/controller-b1.0.0, and@metamask/controller-bdepends on@metamask/controller-a1.1.0.
- For example, this scenario would be valid: a client relies on
- Note, however, that the versions specified in the client's
package.jsonalways "win", and you are expected to keep them up to date so as not to break controller and service intercommunication.
- The dependencies moved are:
- Bump
@metamask/controller-utilsfrom^11.16.0to^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:captureExceptionis no longer an allowed action on the NetworkController messenger. You do not need to delegate itsErrorReportingService:captureExceptionaction to the NetworkController messenger.
- BREAKING: Remove dependency on
@metamask/polling-controller 16.0.1
Changed
- Upgrade
@metamask/utilsfrom^11.8.1to^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-a1.0.0 and@metamask/controller-b1.0.0, and@metamask/controller-bdepends on@metamask/controller-a1.1.0.
- For example, this scenario would be valid: a client relies on
- Note, however, that the versions specified in the client's
package.jsonalways "win", and you are expected to keep them up to date so as not to break controller and service intercommunication.
- The dependencies moved are:
- Bump
@metamask/controller-utilsfrom^11.16.0to^11.18.0(#7534, #7583)
@metamask/sample-controllers 4.0.1
Changed
- Upgrade
@metamask/utilsfrom^11.8.1to^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-a1.0.0 and@metamask/controller-b1.0.0, and@metamask/controller-bdepends on@metamask/controller-a1.1.0.
- For example, this scenario would be valid: a client relies on
- Note, however, that the versions specified in the client's
package.jsonalways "w...
- The dependencies moved are:
747.0.0
@metamask/transaction-controller 62.9.0
Added
- Add optional
targetFiatproperty toMetamaskPayMetadatatype (#7562)
@metamask/transaction-pay-controller 11.0.0
Added
- BREAKING: Support max amount quotes (#7562)
- Add
TransactionPayController:setIsMaxAmountmessenger action. - Add
isMaxAmountproperty toTransactionDatatype. - Add
targetAmountproperty toTransactionPayQuoteandTransactionPayTotals. - Update Relay quote requests to use
EXACT_INPUTtrade type when max amount is selected. - Update totals calculation to account for max amount selection.
- Add
Changed
- Bump
@metamask/controller-utilsfrom^11.17.0to^11.18.0(#7583) - Bump
@metamask/network-controllerfrom^27.1.0to^27.2.0(#7583) - Bump
@metamask/assets-controllersfrom^94.0.0to^95.1.0(#7584, #7600) - Bump
@metamask/transaction-controllerfrom^62.7.0to^62.9.0(#7596, #7602) - Bump
@metamask/bridge-controllerfrom^64.3.0to^64.4.0(#7596) - Bump
@metamask/bridge-status-controllerfrom^64.3.0to^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=trueparameter to token list API calls TokenListControllernow includesrwaDataoptional field inTokenListTokentype to support RWA data in token list retrieval- Reduced
TokenListControllercache time from 24hrs to 4hrs.
- Update token service to include RWA data in API requests by appending
Changed
- Bump
@metamask/multichain-account-servicefrom^4.1.0to^5.0.0(#7594) - Bump
@metamask/transaction-controllerfrom^62.7.0to^62.8.0(#7596) AccountTrackerControllernow 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)