-
Notifications
You must be signed in to change notification settings - Fork 411
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
Upgrade to cosmos-sdk 0.38 #15
Comments
I've created a version that is upgraded to the latest version of the master branch. https://github.com/sikkatech/wasmd/tree/sdk-bump-version Will add as PR once upgraded to official |
Thank you @sunnya97 👍 |
@sunnya97 They are working on rc1 for I merged a bunch in the meantime (esp. 0.6.3 cosmwasm with an overhaul on errors usage in x/wasmd). It would be great if you could rebase on current master and do the update. Note, I don't just want to update the dep, but also merge in any relevant changes to |
Check code hash before gzipping the file
Summary
A new stable release should be out in the next few days. It's much nice to base on that, then on a moving master branch. It also allows other projects to re-use the
x/wasmd
module much easier.Proposal
d6dfa141e2ae38a1ff9f53fca8078c0822671b95
, or about 20 commit).x/wasmd
as needed for compatibiltyThis should also include adding the upgrade module to the core app, which seems to have been done in cosmos/gaia@9823769
Please note that pulling in changes is a bit tricky as we are not a proper fork, but have changed all import paths (so
wasmd
can be used properly as a stand-alone program). This will likely involve more manual work than a simple merge and conflict clean-up (although you can try that first). I think cherry-picking commits one by one may end up the easier. Note that many commits seem minor requirement upgrades and doc improvements, so the number with conflicts should be relatively limited. Here is an idea:but that produces 31 file conflicts, although 22 are in markdown files
For Admin Use
The text was updated successfully, but these errors were encountered: