Skip to content
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

Closed
wants to merge 18 commits into from
Closed

Release v0.41.4 #8737

wants to merge 18 commits into from

Conversation

alessio
Copy link
Contributor

@alessio alessio commented Mar 1, 2021

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.

  • Targeted PR against correct branch (see CONTRIBUTING.md)
  • Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
  • Code follows the module structure standards.
  • Wrote unit and integration tests
  • Updated relevant documentation (docs/) or specification (x/<module>/spec/)
  • Added relevant godoc comments.
  • Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
  • Re-reviewed Files changed in the Github PR explorer
  • Review Codecov Report in the comment section below once CI passes

mergify bot and others added 14 commits February 22, 2021 11:52
Co-authored-by: colin axnér <25233464+colin-axner@users.noreply.github.com>
From: #8641

Co-authored-by: Aleksandr Bezobchuk <aleks.bezobchuk@gmail.com>
* 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>
(cherry picked from commit 5d3f29b)

Co-authored-by: Alessio Treglia <alessio@tendermint.com>
Co-authored-by: Marko <marbar3778@yahoo.com>
(cherry picked from commit eeb3eab)

Co-authored-by: Amaury <1293565+amaurym@users.noreply.github.com>
… (#8708)

* Add warning notice in changelog for v0.41.x bug (ref: #8461) (#8707)

* add disclaimer for v0.41 series for non-hub SDK chains due to #8461

(cherry picked from commit b19ac2c)

Co-authored-by: Cory <cjlevinson@gmail.com>
Co-authored-by: Alessio Treglia <alessio@tendermint.com>
Co-authored-by: Anil Kumar Kammari <anil@vitwit.com>
(cherry picked from commit 897f20b)
Co-authored-by: MD Aleem <72057206+aleem1314@users.noreply.github.com>
Co-authored-by: Marko <marbar3778@yahoo.com>
* auth: allow 0 coin accounts in genesis (#8714)

* allow zero accounts

* fix test

* fix test

(cherry picked from commit a786830)

Co-authored-by: Marko <marbar3778@yahoo.com>
…ch command (#8718) (#8721)

Co-authored-by: Alessio Treglia <alessio@tendermint.com>
(cherry picked from commit 68e7a3a)

Co-authored-by: Barrie Byron <barrie.byron@tendermint.com>
From: #8719
Fixes: #7766

Co-authored-by: Emmanuel T Odeke <emmanuel@orijtech.com>
Co-authored-by: Alessio Treglia <alessio@tendermint.com>
Co-authored-by: Federico Kunze <31522760+fedekunze@users.noreply.github.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>
(cherry picked from commit 3832860)

From: #8730

Co-authored-by: Alessio Treglia <alessio@tendermint.com>
Co-authored-by: Amaury <1293565+amaurym@users.noreply.github.com>
Copy link
Member

@tac0turtle tac0turtle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚢

Copy link
Member

@tac0turtle tac0turtle left a 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

Copy link
Contributor

@shahankhatch shahankhatch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Copy link
Contributor

@amaury1093 amaury1093 left a 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?

@tac0turtle
Copy link
Member

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

@amaury1093
Copy link
Contributor

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 release/* long-living branch, can you confirm?

@alessio
Copy link
Contributor Author

alessio commented Mar 2, 2021

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>
@fdymylja
Copy link
Contributor

fdymylja commented Mar 2, 2021

I have a doubt, isn't the 0 balance change in genesis breaking?

@marbar3778 @AmauryM @alessio

@tac0turtle
Copy link
Member

I have a doubt, isn't the 0 balance change in genesis breaking?

@marbar3778 @AmauryM @alessio

This is only a check. It doesnt alter state. Could you touch on how you see it as breaking?

@fdymylja
Copy link
Contributor

fdymylja commented Mar 2, 2021

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.

(cherry picked from commit 8106056)

Co-authored-by: Marko <marbar3778@yahoo.com>
@sahith-narahari
Copy link
Contributor

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 IO 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?

Copy link
Contributor

@amaury1093 amaury1093 left a 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.

@alessio
Copy link
Contributor Author

alessio commented Mar 2, 2021

Closing and releasing.

Thank you all for the great effort. Keep up the great work!

@alessio alessio closed this Mar 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants