Releases: MetaMask/core
Releases · MetaMask/core
268.0.0
267.0.0
266.0.0
265.0.0
264.0.0
@metamask/transaction-controller 42.0.0
Added
- Retrieve incoming transactions using Accounts API (#4927)
- Add
INCOMING_TRANSACTIONS_SUPPORTED_CHAIN_IDS
constant.
- Add
Changed
- BREAKING: Retrieve incoming transactions using Accounts API (#4927)
- Rename
TransactionControllerIncomingTransactionBlockReceivedEvent
toTransactionControllerIncomingTransactionsReceivedEvent
. - Replace
networkClientIds
argument withchainIds
in following methods:startIncomingTransactionPolling
stopIncomingTransactionPolling
updateIncomingTransactions
- Rename
- Bump
@metamask/eth-block-tracker
from^11.0.2
to^11.0.3
(#5025)
Removed
- BREAKING: Retrieve incoming transactions using Accounts API (#4927)
- Remove
ETHERSCAN_SUPPORTED_NETWORKS
constant. - Remove types:
EtherscanTransactionMeta
RemoteTransactionSource
RemoteTransactionSourceRequest
- Remove
@metamask/user-operation-controller 21.0.0
Changed
263.0.0
@metamask/composable-controller 10.0.0
Changed
- BREAKING:
ComposableController
constructor optioncontrollers
and generic type argumentChildControllers
are re-defined from an array of controller instances to an object that maps controller names to controller instances (#4968) - BREAKING:
ComposableController
class field objectsstate
andmetadata
exclude child controllers that do not extend fromBaseController
orBaseControllerV1
. Any non-controller entries that are passed into the constructor will be removed automatically (#4968) - Bump devDependency
@metamask/json-rpc-engine
from^9.0.3
to^10.0.1
(#4798, #4862)
Fixed
- BREAKING:
ComposableController
class field objectmetadata
now assigns theStateMetadataProperty
-type object{ persist: true, anonymous: true }
to each child controller name (#4968)- Previously, V2 child controllers were erroneously assigned their own metadata object. This issue was introduced in
@metamask/[email protected]
.
- Previously, V2 child controllers were erroneously assigned their own metadata object. This issue was introduced in
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.
- Add the following packages as peer dependencies of this package to satisfy peer dependency requirements from other dependencies:
- 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.
- Add the following packages as peer dependencies of this package to satisfy peer dependency requirements from other dependencies:
- Fix
TokensController.ignoreTokens
so that if a network is provided,allIgnoredTokens
,allTokens
, andallDetectedTokens
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.
- Add the following packages as peer dependencies of this package to satisfy peer dependency requirements from other dependencies:
@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.
- Add the following packages as peer dependencies of this package to satisfy peer dependency requirements from other dependencies:
- 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.
- Add the following packages as peer dependencies of this package to satisfy peer dependency requirements from other dependencies:
- 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.
- Add the following packages as peer dependencies of this package to satisfy peer dependency requirements from other dependencies:
- 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
@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
259.0.0
@metamask/transaction-controller 41.0.0
Added
- BREAKING: Remove global network usage (#4920)
- Add required
networkClientId
argument tohandleMethodData
method.
- Add required
Changed
- BREAKING: Remove global network usage (#4920)
- Require
networkClientId
option inaddTransaction
method. - Require
networkClientId
property inTransactionMeta
type. - Change
wipeTransactions
method arguments to optional object containingaddress
andchainId
properties. - Require
networkClientId
argument inestimateGas
,estimateGasBuffered
andgetNonceLock
methods.
- Require
Removed
- BREAKING: Remove global network usage (#4920)
- Remove the
blockTracker
,isMultichainEnabled
,onNetworkStateChange
andprovider
constructor options. - Remove
filterToCurrentNetwork
option fromgetTransactions
method.
- Remove the
@metamask/user-operation-controller 20.0.0
Changed
- BREAKING: Bump
@metamask/transaction-controller
peer dependency from^40.1.0
to^41.0.0
(#4982)