This repository has been archived by the owner on Oct 7, 2024. It is now read-only.
Releases: MetaMask/eth-hd-keyring
Releases · MetaMask/eth-hd-keyring
7.0.1
Changed
- BREAKING: Update minimum Node.js version from v14 to v16 (#98)
- Bump dependencies (#99)
- BREAKING:
@metamask/eth-sig-util
from^6.0.0
to^7.0.0
- BREAKING:
@metamask/utils
from^5.0.2
to^8.1.0
@ethereumjs/tx
from^4.1.1
to^4.2.0
@ethereumjs/util
from8.0.5
to^8.1.0
ethereum-cryptography
from^1.2.0
to^2.1.2
- BREAKING:
6.0.2
7.0.0 [RETRACTED]
Changed
This version was retracted due to a bug causing code to be missing from the published package. This was addressed in 7.0.1
.
6.0.1 [RETRACTED]
Changed
This version was retracted due to a bug causing code to be missing from the published package. This was addressed in 6.0.2
.
6.0.0
5.0.1
5.0.0
Changed
- BREAKING: Update minimum Node.js version from v12 to v14 (#67)
- BREAKING: Makes version-specific
signTypedData
methods private (#71)- Consumers should use the generic
signTypedData
method and pass the version they'd like as a property in the options argument.
- Consumers should use the generic
- BREAKING: Makes the
wallets
property private (#71)- Consumers should not use this property as it is intended for internal use only.
- BREAKING: Makes
getPrivateKeyFor
a private method (#71)- Consumers who wish to get the private key for a given account should use the
exportAccount
method.
- Consumers who wish to get the private key for a given account should use the
- BREAKING: Bumps browser requirements to those with ES2020 support or greater (#70)
- This change is introduced in update of
@metamask/eth-sig-util
to v5 and new direct dependency onethereumjs/util
v8.0.2
- This change is introduced in update of
- Replaces use of
ethereumjs-wallet
implementation of hdkey with one fromethereum-cryptography
and adapts accordingly. (#69) - Replaces
@metamask/bip39
with@metamask/scure-bip39
(#67)
Removed
4.0.2
Added
- Add parameter validation for constructor /
deserialize
method (#65)- As of v4.0.0, the
deserialize
method (which is also called by the constructor) can no longer generate accounts with thenumberOfAccounts
option without amnemonic
. Prior to v4.0.0, a mnemonic was generated automatically if it was missing, but we now want to ensure a mnemonic is never implicitly generated without the caller knowing.
- As of v4.0.0, the
4.0.1
4.0.0
Changed
- BREAKING: Do not allow re-initialization of keyring instance (#55)
- Consumers are now required to call generateRandomMnemonic() after initialization for creating new SRPs.
- BREAKING: Update minimum Node.js version from v10 to v12 (#45)
- Add
@lavamoat/allow-scripts
(#47)- We now have an allowlist for all post-install scripts. The standard setup script has been added, along with new contributor documentation in the README to explain this script.
- Obfuscate serialized mnemonic (#59)
- Package name changed from
eth-hd-keyring
to@metamask/eth-hd-keyring