Skip to content

6.1.0 #105

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
adonesky1 merged 5 commits into from
Jan 10, 2023
Merged

6.1.0 #105

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
286c2fc
6.1.0
invalid-email-address Jan 9, 2023
ba63cfd
update changelog
adonesky1 Jan 9, 2023
3238a52
Update CHANGELOG.md
adonesky1 Jan 9, 2023
36bc2df
add context for changelog entry
adonesky1 Jan 9, 2023
6503bd7
Update CHANGELOG.md
adonesky1 Jan 10, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

## [6.1.0]
### Changed
- Update BIP-39 implementation from `@scure/bip39` to MetaMask fork version `@metamask/scure-bip39` ([#101](https://github.com/MetaMask/key-tree/pull/101))
Copy link

@mcmire mcmire Jan 9, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know that it's given in the PR, but maybe it's worth explaining what the fork does over the original implementation?

Copy link
Contributor

@adonesky1 adonesky1 Jan 9, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure can do!

Copy link
Contributor

@adonesky1 adonesky1 Jan 9, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done here

- The `@metamask/scure-bip39` fork accepts secret recovery phrases in `Uint8Array` format making it possible to use more secure patterns of passing secret recovery phrases around. This change is non-breaking however, as the `mnemonicToSeed` function used in this package still accepts secret recovery phrases in string format.

## [6.0.0]
### Changed
- BREAKING: Rename all occurrences of `Buffer` with `Bytes` or `Uint8Array` ([#84](https://github.com/MetaMask/key-tree/pull/84))
Expand Down Expand Up @@ -98,7 +103,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
### Added
- Initial release.

[Unreleased]: https://github.com/MetaMask/key-tree/compare/v6.0.0...HEAD
[Unreleased]: https://github.com/MetaMask/key-tree/compare/v6.1.0...HEAD
[6.1.0]: https://github.com/MetaMask/key-tree/compare/v6.0.0...v6.1.0
[6.0.0]: https://github.com/MetaMask/key-tree/compare/v5.0.2...v6.0.0
[5.0.2]: https://github.com/MetaMask/key-tree/compare/v5.0.1...v5.0.2
[5.0.1]: https://github.com/MetaMask/key-tree/compare/v5.0.0...v5.0.1
Expand Down
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@metamask/key-tree",
"version": "6.0.0",
"version": "6.1.0",
"description": "An interface over BIP-32 and BIP-39 key derivation paths.",
"repository": {
"type": "git",
Expand Down