-
Notifications
You must be signed in to change notification settings - Fork 43
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
feat: Cosmos SDK v0.46.0
#914
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #914 +/- ##
===========================================
- Coverage 10.56% 10.55% -0.01%
===========================================
Files 327 327
Lines 75191 75202 +11
===========================================
- Hits 7944 7941 -3
- Misses 67059 67072 +13
- Partials 188 189 +1
|
What difference with #906? Is it with the final imports for IBC and fundraising? |
That PR included all of the changes that I made in the previous PRs to prepare for This PR also fixes tests that were broken by the upgrade.
These are the final imports for a temporary solution. My update to |
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.
Great work
I put some initial comments. I need to do some experimentation and check further the IBC part
Co-authored-by: Lucas Btd <lucas.bertrand.22@gmail.com>
Co-authored-by: Lucas Btd <lucas.bertrand.22@gmail.com>
Supporting the proto changes will be part of ignite/cli#2156 |
Sounds good. If that's the only outstanding issue, are we good to try to get this approved? |
I think this is better if we can merge it once we can run it with If we need the new version for |
I think it would be better the other way around. If this upgrade fully works, then the only remaining issue is with After all, we have now modified our dependencies so that:
|
What does it change if we do This will remove the circular dep, then we just need to update again |
Good point - I was thinking this would introduce a fork in the |
There could be one problem with that because that commit hash wouldn't be guaranteed to be kept forever on Github. The reason for this, once we merge this PR, all the commits here will be squashed into a single commit and the commit that has mentioned will not have a reference on develop PR and also in the base branch of this PR since the branch will be deleted after merging. I suggest merging this PR first and using the commit hash added to the develop branch instead. |
But if we plan to change the commit hash again after we finish work then np. |
Ah - I see what you mean. I just need some approvals and we can merge |
It will be temporary, the time the |
And as soon as this PR is merged we can change it |
In that case there should be no problem. 👍 |
* add .clang-format * setup buf * add scripts and update Makefile * make proto-format * make proto-gen
* cosmos proto Int * remaining cosmos scalar annotations * proto format
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.
Updates the Cosmos SDK to
v0.46.0
. Please review this PR after the other onces I have submitted are completed.This PR builds off of those, and will be much more manageable to review if the other PRs are already merged.
This PR introduces temporary
replace
clauses in ourgo.mod
for the following packages:github.com/cosmos/ibc-go/v5 => github.com/aljo242/ibc-go/v5 v5.1.0
github.com/tendermint/fundraising => github.com/aljo242/fundraising v0.1.2-0.20220726203752-c39abf16b02d
Once the respective repos are updated, we can remove these lines. I have an open PR for
x/fundraising
andibc-go
is near completion.Part of #909
Checklist
These are the criteria that every PR should meet, please check them off as you
review them: