Skip to content

Releases: MetaMask/core

268.0.0

09 Dec 23:16
1fd0d3a
Compare
Choose a tag to compare

@metamask/message-manager 11.0.3

Changed

  • Bump jsonschema from ^1.2.4 to ^1.4.1 (#4998, #5027)

@metamask/queued-request-controller 8.0.2

Changed

  • Bump swappable-obj-proxy from ^2.2.0 to ^2.3.0 (#5036)

@metamask/selected-network-controller 20.0.2

Changed

  • Bump swappable-obj-proxy from ^2.2.0 to ^2.3.0 (#5036)

267.0.0

09 Dec 20:58
5d9f45c
Compare
Choose a tag to compare

@metamask/multichain 1.1.2

Changed

  • Bump @metamask/eth-json-rpc-filters from ^7.0.0 to ^9.0.0 (#5040)

266.0.0

06 Dec 16:50
2fa588d
Compare
Choose a tag to compare

@metamask/network-controller 22.1.1

Changed

  • Bump @metamask/eth-json-rpc-middleware from ^15.0.0 to ^15.0.1 (#5037)
  • Bump swappable-obj-proxy from ^2.2.0 to ^2.3.0 (#5036)
  • Bump @metamask/eth-block-tracker from ^11.0.2 to ^11.0.3 (#5025)

265.0.0

06 Dec 12:37
1df131f
Compare
Choose a tag to compare

@metamask/signature-controller 23.1.0

Changed

  • fix: Fixes in signature decoding functionality (#5028)
  • fix: signature decoding api should be called for typed sign V3 also (#5033)
  • fix: Revert eth-sig-util package (#5027)
  • fix: Update jsonschema version & eth-sig-util (#4998)

264.0.0

06 Dec 10:26
fe00821
Compare
Choose a tag to compare

@metamask/transaction-controller 42.0.0

Added

  • Retrieve incoming transactions using Accounts API (#4927)
    • Add INCOMING_TRANSACTIONS_SUPPORTED_CHAIN_IDS constant.

Changed

  • BREAKING: Retrieve incoming transactions using Accounts API (#4927)
    • Rename TransactionControllerIncomingTransactionBlockReceivedEvent to TransactionControllerIncomingTransactionsReceivedEvent.
    • Replace networkClientIds argument with chainIds in following methods:
      • startIncomingTransactionPolling
      • stopIncomingTransactionPolling
      • updateIncomingTransactions
  • 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

@metamask/user-operation-controller 21.0.0

Changed

  • BREAKING: Bump @metamask/transaction-controller peer dependency from ^41.1.0 to ^42.0.0 (#5032)
  • Bump @metamask/eth-block-tracker from to ^11.0.2 to ^11.0.3 (#5025)

263.0.0

05 Dec 12:36
711ae34
Compare
Choose a tag to compare

@metamask/composable-controller 10.0.0

Changed

  • BREAKING: ComposableController constructor option controllers and generic type argument ChildControllers are re-defined from an array of controller instances to an object that maps controller names to controller instances (#4968)
  • BREAKING: ComposableController class field objects state and metadata exclude child controllers that do not extend from BaseController or BaseControllerV1. 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 object metadata now assigns the StateMetadataProperty-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].

262.0.0

03 Dec 00:51
0c526ee
Compare
Choose a tag to compare

@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...
Read more

261.0.0

28 Nov 19:46
e2cdac9
Compare
Choose a tag to compare

@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

26 Nov 17:42
d1a5dd7
Compare
Choose a tag to compare

@metamask/multichain 1.1.0

Changed

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

259.0.0

26 Nov 16:45
00fa321
Compare
Choose a tag to compare

@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)