-
Notifications
You must be signed in to change notification settings - Fork 546
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.
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
Bump @metamask/key-tree
version
#1114
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1114 +/- ##
=======================================
Coverage 95.16% 95.16%
=======================================
Files 132 132
Lines 4339 4339
Branches 738 738
=======================================
Hits 4129 4129
Misses 210 210 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
packages/rpc-methods/package.json
Outdated
@@ -71,5 +71,11 @@ | |||
"publishConfig": { | |||
"access": "public", | |||
"registry": "https://registry.npmjs.org/" | |||
}, | |||
"lavamoat": { | |||
"allowScripts": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any idea why this was added now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no... not sure. I was prompted to run the allow-scripts
script and did so and it created that diff. But I just removed it and reran the script and it was not added... Not sure what that's about.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed the allowScript
configuration here: 90c5b47
10412e8
to
90c5b47
Compare
Pulls in update to
@metamask/key-tree
in which BIP-39 implementation is updated from@scure/bip39
to MetaMask fork version@metamask/scure-bip39
. The@metamask/scure-bip39
fork accepts secret recovery phrases inUint8Array
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.Even before Snaps switches to passing SRPs as Uint8Arrays this change will be useful by unifying the extension on one BIP-39 implementation reducing redundant code.