-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Bump eth-ledger-bridge-keyring #5791
Conversation
Whoops, just noticed the conflict. I can re-approve after that's resolved. |
Good catch @whymarrh . Just fixed it |
@brunobar79 I think the lockfile might have been resolved incorrectly. I'm seeing 7,582 additions and 7,604 deletions which seems like a lot, it's just the one package that's been bumped here? |
a37176d
to
738ed90
Compare
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.
👍
I think I was using a different node version by accident and that reformatted the whole package-lock.json 😬 As always... good catch @whymarrh! 🙏 |
Just a small note,
If we don't want to close that just yet we should update the description to something like "partial fix for" so that GitHub doesn't auto-close it. GitHub is particular with its wording. |
The new version fixes the error format of the keyring (Now it returns an Error object, as expected by the TX controller) (see MetaMask/eth-ledger-bridge-keyring#8)
Partially addresses #5641