-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Release v0.41.4 #8737
Release v0.41.4 #8737
Conversation
* docs: update master docs (#8353) * bump docs theme to 1.0.180 * add v0.40 to config.js versions * Fix code snippet link * reorganize order of versions * 0.39, 0.41, master * defaulting to 0.41 Co-authored-by: billy rennekamp <billy.rennekamp@gmail.com> Co-authored-by: Amaury Martiny <amaury.martiny@protonmail.com> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit 4c70268) # Conflicts: # docs/package-lock.json * rm package-lock.json, reinstall Co-authored-by: Cyrus Goh <hello@lovincyrus.com>
* Use x/auth/client for querying Txs * Fix lint * Fix small test * update comment * Fix tests * Fix test * Update x/auth/tx/service.go Co-authored-by: Robert Zaremba <robert@zaremba.ch> * Remove context.background Co-authored-by: Robert Zaremba <robert@zaremba.ch>
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.
🚢
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.
blocking to allow other prs to land
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.
lgtm
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.
I have questions: what is the purpose of the release/0.41.4
branch? Is it long-living?
Most importantly, why are we not doing the same thing as for previous 0.41.* releases, i.e. tagging off v0.41.4
off the long-living branch release/v0.41.x
?
This does follow the release procedure outlined on the contributing: https://github.com/cosmos/cosmos-sdk/blob/master/CONTRIBUTING.md#point-release-procedure. It doesn't seem the 0.41 line has been following this practice. If something has changed and the doc hasn't been updated then it should be |
That doc should definitely be updated (cc @clevinson for visibility) 👍, they are not even up-to-date for launchpad. @alessio my understanding is that we agreed in the internal Release Comittee discord chat (from a couple weeks/months ago, re Stargate) to tag releases off the |
Yes I confirm. I opened up this PR to display the CI status and check on the simulations. This PR will not be merged. |
* crypto/keyring: fix offline keys migration (#8639) Fix `keys migrate` command (#8703) crypto/keyring: reinstate the InfoImporter interface InfoImporter is implemented by those Keyring implementations that support import of Info objects. Co-authored-by: Alessio Treglia <alessio@tendermint.com> Co-authored-by: Jonathan Gimeno <jgimeno@gmail.com> Co-authored-by: Amaury <1293565+amaurym@users.noreply.github.com> * refresh golangci-lint * Rename InfoImporter -> LegacyInfoImporter (#8739) Avoid namespace clash with the InfoImporter interface that already exists in the v0.41 release series. * Revert "refresh golangci-lint" This reverts commit 38e1349. Co-authored-by: SaReN <sahithnarahari@gmail.com> Co-authored-by: Jonathan Gimeno <jgimeno@gmail.com> Co-authored-by: Amaury <1293565+amaurym@users.noreply.github.com>
I have a doubt, isn't the 0 balance change in genesis breaking? |
This is only a check. It doesnt alter state. Could you touch on how you see it as breaking? |
I don't have much context because I haven't digged in the issue, but if before it failed (panicked, or returned errors) and now it doesn't then IMO it is breaking. Because something that should have failed does not fail anymore. I don't expect any sdk user to rely on this logic, but still. |
I don't think it's a breaking change, it just alters the response of a command line utility. wdyt? |
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.
Got clarification with Alessio, the release/0.41.4
branch will be deleted once 0.41.4 is out.
Closing and releasing. Thank you all for the great effort. Keep up the great work! |
closes: #8715
DON'T MERGE THIS QUITE YET, please
Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.
docs/
) or specification (x/<module>/spec/
)godoc
comments.Unreleased
section inCHANGELOG.md
Files changed
in the Github PR explorerCodecov Report
in the comment section below once CI passes