Skip to content
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 eth-ledger-bridge-keyring #5791

Merged
merged 1 commit into from
Nov 21, 2018
Merged

Bump eth-ledger-bridge-keyring #5791

merged 1 commit into from
Nov 21, 2018

Conversation

brunobar79
Copy link
Contributor

@brunobar79 brunobar79 commented Nov 20, 2018

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

@metamaskbot
Copy link
Collaborator

Builds ready [1b6dab2]: mascara, chrome, firefox, edge, opera

whymarrh
whymarrh previously approved these changes Nov 20, 2018
@whymarrh
Copy link
Contributor

Whoops, just noticed the conflict. I can re-approve after that's resolved.

@metamaskbot
Copy link
Collaborator

Builds ready [a37176d]: mascara, chrome, firefox, edge, opera

@brunobar79
Copy link
Contributor Author

Whoops, just noticed the conflict. I can re-approve after that's resolved.

Good catch @whymarrh . Just fixed it

@whymarrh
Copy link
Contributor

@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?

Copy link
Contributor

@whymarrh whymarrh left a comment

Choose a reason for hiding this comment

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

👍

@brunobar79
Copy link
Contributor Author

I think I was using a different node version by accident and that reformatted the whole package-lock.json 😬

As always... good catch @whymarrh! 🙏

@whymarrh
Copy link
Contributor

whymarrh commented Nov 21, 2018

Just a small note,

Partially fixes #5641

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.

@metamaskbot
Copy link
Collaborator

Builds ready [738ed90]: mascara, chrome, firefox, edge, opera

@brunobar79 brunobar79 merged commit 80d09d0 into develop Nov 21, 2018
@whymarrh whymarrh deleted the fix-ledger-stuff branch November 21, 2018 02:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants