-
Notifications
You must be signed in to change notification settings - Fork 17
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
chore(dev-deps): update ledger-cosmos-go from v0.12.2 to v0.12.4 and ledger-go from v0.14.1 to v0.14.3 #145
chore(dev-deps): update ledger-cosmos-go from v0.12.2 to v0.12.4 and ledger-go from v0.14.1 to v0.14.3 #145
Conversation
Co-authored-by: John Letey <[email protected]>
Co-authored-by: John Letey <[email protected]>
Co-authored-by: John Letey <[email protected]>
Co-authored-by: Max Breithecker <[email protected]>
Co-authored-by: John Letey <[email protected]>
Co-authored-by: Troy Kessler <[email protected]> Co-authored-by: mbreithecker <[email protected]>
Co-authored-by: John Letey <[email protected]>
Co-authored-by: Troy Kessler <[email protected]>
Co-authored-by: rapha <[email protected]> Co-authored-by: mbreithecker <[email protected]>
Co-authored-by: Jeremy Martin-Cocher <[email protected]>
Co-authored-by: mbreithecker <[email protected]>
Hey @zakarialounes , |
Indeed, I started from tag v1.3.1. So I'm closing this PR since it's of no use. Thank you. |
What's strange @mbreithecker is that GitHub detects a change, since it allowed me to create the PR. I'll leave it to you to check whether the change is actually there. |
5b5cc34
to
0651828
Compare
I thought that GitHub would detect that the changes were already there, but obviously it's having trouble. Since the changes are there, I'm closing the PR. |
You are right, this is indeed very strange. I also did a diff on my local machine and apparently Github is having some troubles. |
Please see: