Skip to content

Tags: MetaMask/core

Tags

v345.0.0

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Release/345.0.0 (#5550)

## @metamask/chain-agnostic-permission

## [0.3.0]

### Added

- Export `KnownSessionProperties` enum
([#5522](#5522))
- Add more chain agnostic utility functions for interfacing w/ caip25
permission ([#5536](#5536))
- New `setPermittedAccounts` function that allows setting accounts for
any CAIP namespace, not just EVM scopes.
- New `addPermittedChainId` and `setPermittedChainIds` functions for
managing permitted chains across any CAIP namespace.
- New `generateCaip25Caveat` function to generate a valid
`endowment:caip25` permission caveat from given accounts and chains of
any CAIP namespace.
- New `isWalletScope` utility function to detect wallet-related scopes.

### Changed

- **BREAKING:** An error is now thrown in the caveat validator when a
`caip25:endowment` permission caveat has no scopes in either
`requiredScopes` or `optionalScopes`
([#5548](#5548))

v344.0.0

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Release 344.0.0 (#5547)

Minor release of `@metamask/transaction-controller`.

v343.0.0

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Release 343.0.0 (#5542)

v342.0.0

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Release/342.0.0 (#5538)

## Explanation

<!--
Thanks for your contribution! Take a moment to answer these questions so
that reviewers have the information they need to properly understand
your changes:

* What is the current state of things and why does it need to change?
* What is the solution your changes offer and how does it work?
* Are there any changes whose purpose might not obvious to those
unfamiliar with the domain?
* If your primary goal was to update one package but you found you had
to update another one along the way, why did you do so?
* If you had to upgrade a dependency, why did you do so?
-->
This release updates some of the method arguments for the
`earn-controller` and updates the `selectedAccountChange` subscription
handler to pass the `account?.address` from the event payload to the
underlying methods.

See changelog for further details.

---------

Co-authored-by: cryptodev-2s <109512101+cryptodev-2s@users.noreply.github.com>

v306.0.1

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Release 344.0.0 (#5543)

@metamask/transaction-controller@52.2.0

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Release 344.0.0 (#5547)

Minor release of `@metamask/transaction-controller`.

@metamask/keyring-controller@21.0.1

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Release 343.0.0 (#5542)

@metamask/keyring-controller@19.2.2

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Release 344.0.0 (#5543)

@metamask/earn-controller@0.10.0

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Release/342.0.0 (#5538)

## Explanation

<!--
Thanks for your contribution! Take a moment to answer these questions so
that reviewers have the information they need to properly understand
your changes:

* What is the current state of things and why does it need to change?
* What is the solution your changes offer and how does it work?
* Are there any changes whose purpose might not obvious to those
unfamiliar with the domain?
* If your primary goal was to update one package but you found you had
to update another one along the way, why did you do so?
* If you had to upgrade a dependency, why did you do so?
-->
This release updates some of the method arguments for the
`earn-controller` and updates the `selectedAccountChange` subscription
handler to pass the `account?.address` from the event payload to the
underlying methods.

See changelog for further details.

---------

Co-authored-by: cryptodev-2s <109512101+cryptodev-2s@users.noreply.github.com>

@metamask/chain-agnostic-permission@0.3.0

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Release/345.0.0 (#5550)

## @metamask/chain-agnostic-permission

## [0.3.0]

### Added

- Export `KnownSessionProperties` enum
([#5522](#5522))
- Add more chain agnostic utility functions for interfacing w/ caip25
permission ([#5536](#5536))
- New `setPermittedAccounts` function that allows setting accounts for
any CAIP namespace, not just EVM scopes.
- New `addPermittedChainId` and `setPermittedChainIds` functions for
managing permitted chains across any CAIP namespace.
- New `generateCaip25Caveat` function to generate a valid
`endowment:caip25` permission caveat from given accounts and chains of
any CAIP namespace.
- New `isWalletScope` utility function to detect wallet-related scopes.

### Changed

- **BREAKING:** An error is now thrown in the caveat validator when a
`caip25:endowment` permission caveat has no scopes in either
`requiredScopes` or `optionalScopes`
([#5548](#5548))