Releases: MetaMask/core
Releases · MetaMask/core
696.0.0
@metamask/shield-controller 3.1.0
Added
- Added
AuthorizationListin transaction init and log requests for 7702 transactions. (#7246)
Changed
- Move peer dependencies for controller and service packages to direct dependencies (#7209, #7220, #7236)
- The dependencies moved are:
@metamask/signature-controller(^37.0.0)@metamask/transaction-controller(^62.3.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:
@metamask/subscription-controller 5.1.0
Changed
- Removed
minBalanceUSDfield from theSubscriptionEligibilitytype. (#7248) - Updated
submitShieldSubscriptionCryptoApprovalto handle change payment method transaction if subscription already existed (#7231) - Bump
@metamask/transaction-controllerfrom^62.0.0to^62.3.0(#7215, #7220, #7236) - Move peer dependencies for controller and service packages to direct dependencies (#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-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:
695.0.0
@metamask/bridge-controller 63.2.0
Changed
- Update
stopPollingForQuotesto accept metrics context for the QuotesReceived event. If context is provided and quotes are still loading when the handler is called, theUnified SwapBridge Quotes Receivedis published before the poll is cancelled (#7242)
@metamask/bridge-status-controller 63.1.0
Changed
- Bump
@metamask/bridge-controllerfrom^63.1.0to^63.2.0(#7245) - Move peer dependencies for controller and service packages to direct dependencies (#7209, #7220, #7236)
- 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.3.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/bridge-controllerfrom^63.0.0to^63.1.0(#7238)
Removed
- Remove direct QuotesReceived event publishing to avoid race conditions that can happen when clients navigate and reset state. Update
submitTxto accept quotesReceivedContext (replace isLoading/warnings) and propagate context to the BridgeController through the `stopPollingForQuotes call (#7242)
694.0.0
@metamask/bridge-controller 63.1.0
Added
- Port the following constants from
SwapsControllerand export them:SWAPS_TESTNET_CHAIN_ID,SWAPS_CONTRACT_ADDRESSES,SWAPS_WRAPPED_TOKENS_ADDRESSES,ALLOWED_CONTRACT_ADDRESSES(#7233) - Port the following utils from
SwapsControllerand export them:isValidSwapsContractAddress,getSwapsContractAddress(#7233)
Changed
- Move peer dependencies for controller and service packages to direct dependencies (#7209, #7220, #7236)
- 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.3.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:
Fixed
- Update
quotesLoadingStatusto "LOADING" if a balance fetch is needed before fetching quotes ((https://github.com/MetaMask/core/pull/7227)[#7227]) - Wait for async SSE message handlers before updating
quotesLoadingStatusto prevent clients from displaying "No quotes" warnings ((https://github.com/MetaMask/core/pull/7227)[#7227])
693.0.0
692.0.0
@metamask/transaction-pay-controller 10.1.0
Added
- Use new feature flags to configure gas limit fallback for Relay quotes (#7229)
- Use gas fee properties from Relay quotes.
Changed
- Move peer dependencies for controller and service packages to direct dependencies (#7209, #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.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-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:
691.0.0
@metamask/transaction-controller 62.2.0
Added
- Add
musdConversiontransaction type (#7218)
Changed
- Move peer dependencies for controller and service packages to direct dependencies (#7209)
- The dependencies moved are:
@metamask/accounts-controller(^35.0.0)@metamask/approval-controller(^8.0.0)@metamask/gas-fee-controller(^26.0.0)@metamask/network-controller(^26.0.0)@metamask/remote-feature-flag-controller(^2.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:
690.0.0
689.0.0
688.0.0
@metamask/assets-controllers 91.0.0
Changed
- BREAKING: Update
spot-pricesendpoint to use Price API v3 (#7119)- Update
AbstractTokenPricesService.fetchTokenPricesarguments and return type - Update
CodefiTokenPricesServiceV2list of supported currencies - Update
TokenRatesControllerto fetch prices by native currency instead of by chain - Remove legacy polling code and unused events from
TokenRatesController
- Update
@metamask/bridge-controller 63.0.0
Changed
- BREAKING: Bump
@metamask/assets-controllersfrom^90.0.0to^91.0.0(#7207)
@metamask/bridge-status-controller 63.0.0
Changed
- BREAKING: Bump
@metamask/bridge-controllerfrom^62.0.0to^63.0.0(#7207)
@metamask/transaction-pay-controller 10.0.0
Added
- Use gas fee token for Relay deposit transactions if insufficient native balance (#7193)
- Add optional
fees.isSourceGasFeeTokenproperty toTransactionPayQuoteandTransactionPayTotalstype.
- Add optional
Changed
687.0.0
@metamask/account-tree-controller 4.0.0
Changed
- BREAKING: Bump
@metamask/profile-sync-controllerfrom^26.0.0to^27.0.0(#7202) - BREAKING: Bump
@metamask/multichain-account-servicefrom^3.0.0to^4.0.0(#7202) - BREAKING: Bump
@metamask/keyring-controllerfrom^24.0.0to^25.0.0(#7202) - BREAKING: Bump
@metamask/accounts-controllerfrom^34.0.0to^35.0.0(#7202)
@metamask/accounts-controller 35.0.0
Changed
- BREAKING: Bump
@metamask/network-controllerfrom^25.0.0to^26.0.0(#7202) - BREAKING: Bump
@metamask/keyring-controllerfrom^24.0.0to^25.0.0(#7202)
@metamask/address-book-controller 7.0.1
Changed
- Bump
@metamask/controller-utilsfrom^11.15.0to^11.16.0(#7202)
@metamask/assets-controllers 90.0.0
Added
- Added optional filtering of Tron staking tokens (energy, bandwidth) in asset selectors
selectAssetsBySelectedAccountGroup(defaults totrue) (#7198)
Changed
- Bump
@metamask/polling-controllerfrom^15.0.0to^16.0.0(#7202) - Bump
@metamask/controller-utilsfrom^11.15.0to^11.16.0(#7202) - BREAKING: Bump
@metamask/transaction-controllerfrom^61.0.0to^62.0.0(#7202) - BREAKING: Bump
@metamask/preferences-controllerfrom^21.0.0to^22.0.0(#7202) - BREAKING: Bump
@metamask/phishing-controllerfrom^15.0.0to^16.0.0(#7202) - BREAKING: Bump
@metamask/network-controllerfrom^25.0.0to^26.0.0(#7202) - BREAKING: Bump
@metamask/keyring-controllerfrom^24.0.0to^25.0.0(#7202) - BREAKING: Bump
@metamask/core-backendfrom^4.1.0to^5.0.0(#7202) - BREAKING: Bump
@metamask/accounts-controllerfrom^34.0.0to^35.0.0(#7202) - BREAKING: Bump
@metamask/account-tree-controllerfrom^3.0.0to^4.0.0(#7202)
@metamask/bridge-controller 62.0.0
Added
- Add and export
getQuotesReceivedPropertiesutility to build the metrics payload for clients (#7182)
Changed
- Bump
@metamask/polling-controllerfrom^15.0.0to^16.0.0(#7202) - Bump
@metamask/multichain-network-controllerfrom^2.0.0to^3.0.0(#7202) - Bump
@metamask/gas-fee-controllerfrom^25.0.0to^26.0.0(#7202) - Bump
@metamask/controller-utilsfrom^11.15.0to^11.16.0(#7202) - BREAKING: Bump
@metamask/transaction-controllerfrom^61.0.0to^62.0.0(#7202) - BREAKING: Bump
@metamask/network-controllerfrom^25.0.0to^26.0.0(#7202) - BREAKING: Bump
@metamask/assets-controllersfrom^89.0.0to^90.0.0(#7202) - BREAKING: Bump
@metamask/accounts-controllerfrom^34.0.0to^35.0.0(#7202)
@metamask/bridge-status-controller 62.0.0
Changed
- Bump
@metamask/polling-controllerfrom^15.0.0to^16.0.0(#7202) - Bump
@metamask/controller-utilsfrom^11.15.0to^11.16.0(#7202) - BREAKING: Bump
@metamask/transaction-controllerfrom^61.0.0to^62.0.0(#7202) - BREAKING: Bump
@metamask/network-controllerfrom^25.0.0to^26.0.0(#7202) - BREAKING: Bump
@metamask/gas-fee-controllerfrom^25.0.0to^26.0.0(#7202) - BREAKING: Bump
@metamask/bridge-controllerfrom^61.0.0to^62.0.0(#7202) - BREAKING: Bump
@metamask/accounts-controllerfrom^34.0.0to^35.0.0(#7202) - Update
submitTxhandler to accept optionalisLoadingandwarningsarguments. WhenisLoading=true, the QuotesReceived event is published (#7182)
@metamask/controller-utils 11.16.0
Added
- Add
getCircuitStatemethod toServicePolicy(#7164)- This can be used when working with a chain of services to know whether a service's underlying circuit is open or closed.
- Add
onAvailablemethod toServicePolicy(#7164)- This can be used to listen for the initial successful execution of the service, or the first successful execution after the service becomes degraded or the circuit breaks.
- Add
resetmethod toServicePolicy(#7164)- This can be used when working with a chain of services to reset the state of the circuit breaker policy (e.g. if a primary recovers and we want to reset the failovers).
- Export
CockatielEventEmitterandCockatielFailureReasonfrom Cockatiel (#7164)- These can be used to further transform types for event emitters/listeners.
@metamask/core-backend 5.0.0
Changed
- Bump
@metamask/profile-sync-controllerfrom^26.0.0to^27.0.0(#7202) - Bump
@metamask/controller-utilsfrom^11.15.0to^11.16.0(#7202) - BREAKING: Bump
@metamask/keyring-controllerfrom^24.0.0to^25.0.0(#7202) - BREAKING: Bump
@metamask/accounts-controllerfrom^34.0.0to^35.0.0(#7202)
@metamask/delegation-controller 2.0.0
Changed
- BREAKING: Bump
@metamask/keyring-controllerfrom^24.0.0to^25.0.0(#7202) - BREAKING: Bump
@metamask/accounts-controllerfrom^34.0.0to^35.0.0(#7202)
@metamask/earn-controller 11.0.0
Changed
- Bump
@metamask/controller-utilsfrom^11.15.0to^11.16.0(#7202) - BREAKING: Bump
@metamask/network-controllerfrom^25.0.0to^26.0.0(#7202) - BREAKING: Bump
@metamask/account-tree-controllerfrom^3.0.0to^4.0.0(#7202)
@metamask/ens-controller 19.0.0
Changed
- Bump
@metamask/controller-utilsfrom^11.15.0to^11.16.0(#7202) - BREAKING: Bump
@metamask/network-controllerfrom^25.0.0to^26.0.0(#7202)
@metamask/eth-block-tracker 15.0.0
Added
- Add
Contextgeneric parameter toPollingBlockTracker(#7061)- This enables passing providers with different context types to the block tracker.
Changed
- Bump
@metamask/eth-json-rpc-providerfrom^5.0.1to^6.0.0(#7202) - BREAKING: Use
InternalProviderinstead ofSafeEventEmitterProvider(#6796)- The block tracker expects a provider with an
InternalProviderinstead of aSafeEventEmitterProvider.
- The block tracker expects a provider with an
- BREAKING: Migrate to
JsonRpcEngineV2(#7001)
@metamask/eth-json-rpc-middleware 22.0.0
Added
- Add new function
providerAsMiddlewareV2for converting anInternalProviderinto aJsonRpcEnginev2-compatible middleware (#7138)
Changed
- BREAKING: Migrate all middleware from
JsonRpcEnginetoJsonRpcEngineV2(#7065)- To continue using this package with the legacy
JsonRpcEngine, use theasLegacyMiddlewarebackwards compatibility function.
- To continue using this package with the legacy
- BREAKING: Change the signatures of hooks for
createWalletMiddleware(#7065)- To wit:
getAccountstakes an origin argument (string) instead of aJsonRpcRequestprocessDecryptMessageandprocessEncryptionPublicKeytake aMessageRequestfrom@metamask/message-managerinstead ofJsonRpcRequestprocessPersonalMessage,processTransaction,processSignTransaction,processTypedMessage,processTypedMessageV3andprocessTypedMessageV4take acontextas the third argument, before any other arguments
- Be advised that request objects are now deeply frozen, and cannot be mutated.
- To wit:
- BREAKING: Use
InternalProviderinstead ofSafeEventEmitterProvider(#6796)- Wherever a
SafeEventEmitterProviderwas expected, anInternalProvideris now expected instead.
- Wherever a
- BREAKING: Stop retrying
undefinedresults for methods that include a block...