All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- Add keyring state migration framework (#505)
- Use
createMigrations().add(...)to build a chain of versioned migration steps, and.apply(state)to migrate the internal state of keyrings
- Use
- Add
EthKeyringV1Adapterand typed errors for adapting v2 ETH keyrings to legacy ETH keyring signing flows (#555)
- Bump
@metamask/keyring-apifrom^23.1.0to^23.2.0(#562)
- Bump
@metamask/keyring-utilsfrom^3.3.0to^3.3.1(#546)
- Add
KeyringV1Adapter(#543)- This adapter can be used when a keyring v2 instance has no v1 equivalent (
KeyringControllerstill rely on v1 logic for its vault/state management).
- This adapter can be used when a keyring v2 instance has no v1 equivalent (
- Bump
@metamask/keyring-utilsfrom^3.2.0to^3.3.0(#544)
- Bump
@metamask/keyring-apifrom^23.0.1to^23.1.0(#538)
- Bump
@metamask/keyring-apifrom^23.0.0to^23.0.1(#518)
- Workaround Browserify subpath export for
/v2(#516)
- Add
./v2subpath export for keyring v2 building blocks (#513)KeyringWrapper,EthKeyringWrapper,EthKeyringMethod, andEthKeyringWrapperOptionsare now available from@metamask/keyring-sdk/v2.
- BREAKING: Move
KeyringWrapperandEthKeyringWrapper(and related types) to the new./v2subpath export (#513)- Use
import { KeyringWrapper, EthKeyringWrapper, EthKeyringMethod } from '@metamask/keyring-sdk/v2'instead. KeyringAccountRegistry,encodeMnemonic, andgenerateEthAccountIdremain available from the main entry point.
- Use
- Bump
@metamask/utilsfrom^11.10.0to^11.11.0(#483) - Bump
@metamask/keyring-apifrom^22.0.0to^23.0.0(#515)
- Add
generateIdoption toKeyringAccountRegistry(#503) - Add
generateEthAccountIdto generate deterministic account IDs for EVM addresses, and use it by default inEthKeyringWrapper(#504)
- Add
encodeMnemonic(#495)
- Bump
@metamask/utilsfrom^11.1.0to^11.10.0(#489)