209.0.0

@metamask/profile-sync-controller 0.9.3

Fixed

• Only fire onAccountNameUpdated when account name has changed (#4735)

208.0.0

@metamask/accounts-controller 18.2.2

Changed

• Bump accounts related packages (#4713), (#4728)
  • Those packages are now built slightly differently and are part of the accounts monorepo.
  • Bump @metamask/keyring-api from ^8.1.0 to ^8.1.4
  • Bump @metamask/eth-snap-keyring from ^4.3.3 to ^4.3.6

@metamask/approval-controller 7.1.0

Added

• Add deleteAfterResult option to accept method to delay removal of approval request from state (#4715)

@metamask/assets-controllers 38.1.0

Changed

• Parallelization of detected tokens with balance (#4697)
• Bump accounts related packages (#4713), (#4728)
  • Those packages are now built slightly differently and are part of the accounts monorepo.
  • Bump @metamask/keyring-api from ^8.1.0 to ^8.1.4

@metamask/chain-controller 0.1.3

Changed

• Bump accounts related packages (#4713), (#4728)
  • Those packages are now built slightly differently and are part of the accounts monorepo.
  • Bump @metamask/keyring-api from ^8.1.0 to ^8.1.4

@metamask/keyring-controller 17.2.2

Changed

• Bump accounts related packages (#4713), (#4728)
  • Those packages are now built slightly differently and are part of the accounts monorepo.
  • Bump @metamask/keyring-api from ^8.1.0 to ^8.1.4
  • Bump @metamask/eth-hd-keyring from ^7.0.1 to ^7.0.4
  • Bump @metamask/eth-simple-keyring from ^6.0.1 to ^6.0.5

@metamask/notification-controller 7.0.0

Changed

• BREAKING: The show function now uses an option bag rather than a single string (#4682)
  • This will be used to persist the extra properties needed to show JSX content in Snap notifications.

@metamask/notification-services-controller 0.8.1

Changed

• Bump @metamask/keyring-controller from ^17.2.1 to ^17.2.2. (#4731)
• Bump @metamask/profile-sync-controller from ^0.9.1 to ^0.9.2. (#4731)

@metamask/profile-sync-controller 0.9.2

Changed

• Bump accounts related packages (#4713), (#4728)
  • Those packages are now built slightly differently and are part of the accounts monorepo.
  • Bump @metamask/keyring-api from ^8.1.0 to ^8.1.4

@metamask/transaction-controller 37.1.0

Added

• Populate submitHistory in state when submitting transactions to network (#4706)
• Export CHAIN_IDS, ETHERSCAN_SUPPORTED_NETWORKS and SPEED_UP_RATE constants (#4706)

Changed

• Make getPermittedAccounts constructor callback optional (#4706)
• Bump accounts related packages (#4713), (#4728)
  • Those packages are now built slightly differently and are part of the accounts monorepo.
  • Bump @metamask/keyring-api from ^8.1.0 to ^8.1.4

207.0.0

@metamask/profile-sync-controller 0.9.1

Changed

• improve account syncing performance (#4726)
  • check if isEvmAccountType before saving an account in user storage in account syncing
  • check for correct KeyringType before saving an account in user storage in account syncing
  • wait for AccountsController:accountAdded event to fire before adding another account in account syncing
• update 'eth-{simple,hd,snap}-keyring' + 'keyring-api' (#4713)

206.0.0

@metamask/profile-sync-controller 0.9.0

Added

• add batch PUT endpoint for account syncing (#4724)
• add batch PUT endpoint support (#4723)

205.0.0

@metamask/notification-services-controller 0.8.0

Changed

• Update UI export from MATIC to POL (#4720)
• Bump @metamask/profile-sync-controller from ^0.8.0 to ^0.8.1 ([#4722]#4720)

@metamask/profile-sync-controller 0.8.1

Changed

• move and organize shared profile sync dependencies (#4717)

Fixed

• fix: profile-sync-controller mobile compilation issues (#4721)
  • mobile does not support exported async arrow functions, so needed to convert these into normal async functions

204.0.0

@metamask/notification-services-controller 0.7.0

Changed

• Bump @metamask/profile-sync-controller from ^0.7.0 to ^0.8.0 (#4712)

Fixed

• BREAKING use new profile-sync notification settings path hash (#4711)
  • changing this path also means the underlying storage hash has changed. But this will align with our existing solutions that are in prod.

@metamask/profile-sync-controller 0.8.0

Fixed

• BREAKING update profile-sync notification settings path hash (#4711)
  • changing this path also means the underlying storage hash has changed. But this will align with our existing solutions that are in prod.

203.0.0

@metamask/notification-services-controller 0.6.0

Changed

• update subpath exports to use new .d.cts definition files. (#4709)
• Bump @metamask/profile-sync-controller from ^0.6.0 to ^0.7.0 (#4710)

@metamask/profile-sync-controller 0.7.0

Changed

• update subpath exports to use new .d.cts definition files. (#4709)
• move profile-sync-sdk snap methods to snap auth class (#4708)
  • move and validate connectSnap and isSnapConnected methods to only be available for SRP auth.

Removed

• test: remove unused test mock (#4703)

202.0.0

@metamask/accounts-controller 18.2.1

Changed

• Bump @metamask/eth-snap-keyring from ^4.3.1 to ^4.3.3 (#4689)
• Bump @metamask/snaps-sdk from ^6.1.1 to ^6.5.0 (#4689)
• Bump @metamask/snaps-utils from ^7.8.1 to ^8.1.1 (#4689)
• Bump peer dependency @metamask/snaps-controllers from ^9.3.0 to ^9.7.0 (#4689)

Fixed

• Produce and export ESM-compatible TypeScript type declaration files in addition to CommonJS-compatible declaration files (#4648)
  • Previously, this package shipped with only one variant of type declaration
    files, and these files were only CommonJS-compatible, and the exports
    field in package.json linked to these files. This is an anti-pattern and
    was rightfully flagged by the
    "Are the Types Wrong?" tool as
    "masquerading as CJS".
    All of the ATTW checks now pass.
• Remove chunk files (#4648).
  • Previously, the build tool we used to generate JavaScript files extracted
    common code to "chunk" files. While this was intended to make this package
    more tree-shakeable, it also made debugging more difficult for our
    development teams. These chunk files are no longer present.

@metamask/address-book-controller 6.0.1

Fixed

• Produce and export ESM-compatible TypeScript type declaration files in addition to CommonJS-compatible declaration files (#4648)
  • Previously, this package shipped with only one variant of type declaration
    files, and these files were only CommonJS-compatible, and the exports
    field in package.json linked to these files. This is an anti-pattern and
    was rightfully flagged by the
    "Are the Types Wrong?" tool as
    "masquerading as CJS".
    All of the ATTW checks now pass.
• Remove chunk files (#4648).
  • Previously, the build tool we used to generate JavaScript files extracted
    common code to "chunk" files. While this was intended to make this package
    more tree-shakeable, it also made debugging more difficult for our
    development teams. These chunk files are no longer present.

@metamask/announcement-controller 7.0.1

Changed

• Bump TypeScript from ~4.9.5 to ~5.2.2 and set moduleResolution option to Node16 (#3645, #4576, #4584)

Fixed

• Produce and export ESM-compatible TypeScript type declaration files in addition to CommonJS-compatible declaration files (#4648)
  • Previously, this package shipped with only one variant of type declaration
    files, and these files were only CommonJS-compatible, and the exports
    field in package.json linked to these files. This is an anti-pattern and
    was rightfully flagged by the
    "Are the Types Wrong?" tool as
    "masquerading as CJS".
    All of the ATTW checks now pass.
• Remove chunk files (#4648).
  • Previously, the build tool we used to generate JavaScript files extracted
    common code to "chunk" files. While this was intended to make this package
    more tree-shakeable, it also made debugging more difficult for our
    development teams. These chunk files are no longer present.

@metamask/approval-controller 7.0.4

Fixed

• Produce and export ESM-compatible TypeScript type declaration files in addition to CommonJS-compatible declaration files (#4648)
  • Previously, this package shipped with only one variant of type declaration
    files, and these files were only CommonJS-compatible, and the exports
    field in package.json linked to these files. This is an anti-pattern and
    was rightfully flagged by the
    "Are the Types Wrong?" tool as
    "masquerading as CJS".
    All of the ATTW checks now pass.
• Remove chunk files (#4648).
  • Previously, the build tool we used to generate JavaScript files extracted
    common code to "chunk" files. While this was intended to make this package
    more tree-shakeable, it also made debugging more difficult for our
    development teams. These chunk files are no longer present.

@metamask/assets-controllers 38.0.1

Fixed

• Produce and export ESM-compatible TypeScript type declaration files in addition to CommonJS-compatible declaration files (#4648)
  • Previously, this package shipped with only one variant of type declaration
    files, and these files were only CommonJS-compatible, and the exports
    field in package.json linked to these files. This is an anti-pattern and
    was rightfully flagged by the
    "Are the Types Wrong?" tool as
    "masquerading as CJS".
    All of the ATTW checks now pass.
• Remove chunk files (#4648).
  • Previously, the build tool we used to generate JavaScript files extracted
    common code to "chunk" files. While this was intended to make this package
    more tree-shakeable, it also made debugging more difficult for our
    development teams. These chunk files are no longer present.
• Don't update currency rates on transient errors (#4662)
  • In CurrencyRateController if unexpected errors occur during requests to
    crypto compare, the conversion rate in state will remain unchanged instead
    of being set to null.
• Fix fallback conversion rate for token market data (#4615)
  • On networks where the native currency is not ETH, token market data is now
    correctly priced in the native currency.

@metamask/base-controller 7.0.1

Fixed

• Produce and export ESM-compatible TypeScript type declaration files in addition to CommonJS-compatible declaration files (#4648)
  • Previously, this package shipped with only one variant of type declaration
    files, and these files were only CommonJS-compatible, and the exports
    field in package.json linked to these files. This is an anti-pattern and
    was rightfully flagged by the
    "Are the Types Wrong?" tool as
    "masquerading as CJS".
    All of the ATTW checks now pass.
• Remove chunk files (#4648).
  • Previously, the build tool we used to generate JavaScript files extracted
    common code to "chunk" files. While this was intended to make this package
    more tree-shakeable, it also made debugging more difficult for our
    development teams. These chunk files are no longer present.

@metamask/build-utils 3.0.1

Changed

• Bump @metamask/utils from ^8.3.0 to ^9.1.0 (#4516, #4529)
• Bump @metamask/rpc-errors from ^6.2.1 to ^6.3.1 (#4516)
• Bump TypeScript from ~4.9.5 to ~5.2.2 and set moduleResolution option to Node16 (#3645, #4576, #4584)

Fixed

• Produce and export ESM-compatible TypeScript type declaration files in addition to CommonJS-compatible declaration files (#4648)
  • Previously, this package shipped with only one variant of type declaration
    files, and these files were only CommonJS-compatible, and the exports
    field in package.json linked to these files. This is an anti-pattern and
    was rightfully flagged by the
    "Are the Types Wrong?" tool as
    "masquerading as CJS".
    All of the ATTW checks now pass.
• Remove chunk files (#4648).
  • Previously, the build tool we used to generate JavaScript files extracted
    common code to "chunk" files. While this was intended to make this package
    more tree-shakeable, it also made debugging more difficult for our
    development teams. These chunk files are no longer present.

@metamask/chain-controller 0.1.2

Changed

• Bump @metamask/keyring-api from ^8.0.1 to ^8.1.0 (#4594)
• Bump TypeScript from ~4.9.5 to ~5.2.2 and set moduleResolution option to Node16 (#3645, #4576, #4584)

Fixed

• Produce and export ESM-compatible TypeScript type decla...

201.0.0

@metamask/transaction-controller 36.1.0

Added

• Add missing TransactionControllerOptions type in package-level export (#4683)

200.0.0

@metamask/accounts-controller 18.2.0

Added

• Add event AccountsController:accountRenamed and export corresponding event type AccountsControllerAccountRenamedEvent (#4664), (#4660)
• Add new nameLastUpdatedAt timestamp to account's metadata (#4589)

Changed

• Consolidate setAccountName logic in updateAccountMetadata (#4663)
  • Moved the logic for checking account name uniqueness and triggering the accountRenamed event fromsetAccountName to updateAccountMetadata. The setAccountName method now callsupdateAccountMetadata to handle these tasks.