-
Notifications
You must be signed in to change notification settings - Fork 352
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
Problem: ibc-go is not upgraded to v4.0.0-rc2 #826
Conversation
Solution: Upgraded ibc-go to v4.0.0-rc2 and changed wasmd to different patched version
Codecov Report
@@ Coverage Diff @@
## master #826 +/- ##
==========================================
+ Coverage 18.29% 20.77% +2.48%
==========================================
Files 98 98
Lines 10761 10944 +183
==========================================
+ Hits 1969 2274 +305
+ Misses 8341 8181 -160
- Partials 451 489 +38
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. |
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.
do you need a help to push the patched branch on github.com/crypto-org-chain/wasmd ?
I don't have write permissions on our fork. Can you push this branch to our fork? https://github.com/devashishdxt/wasmd/tree/ibc-4.0.0 |
Solution: Upgraded ibc-go to v4.0.0-rc2 and changed wasmd to different patched version
Solution: Upgraded ibc-go to v4.0.0-rc2 and changed wasmd to different patched version
Solution: Upgraded ibc-go to v4.0.0-rc2 and changed wasmd to different patched version.