-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Update changelog on master (from v0.40.x branch) #7528
Conversation
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.
Why do this now and not when we officially release v0.40.0?
I think this would be useful to have rc-level changelog sections for more granular visibility of what subsequent bugfixes / additions get made in each release candidate. This is me following the process that I saw tendermint using for their v0.34 release process. My intention would be to squash the rc CHANGELOG sections into a single section for v0.40.0 once we publish the release. In the meantime, this is just meant to add better readability for folks tracking the RC process, who likely want to know which bugfixes make it into each RC. |
* (modules) [\#6311](https://github.com/cosmos/cosmos-sdk/issues/6311) Remove `alias.go` usage | ||
* (x/auth) [\#6443](https://github.com/cosmos/cosmos-sdk/issues/6443) Move `FeeTx` and `TxWithMemo` interfaces from `x/auth/ante` to `types`. | ||
* (modules) [\#6447](https://github.com/cosmos/cosmos-sdk/issues/6447) Rename `blacklistedAddrs` to `blockedAddrs`. | ||
* (kvstore) [\#7415](https://github.com/cosmos/cosmos-sdk/pull/7415) Allow new stores to be registered during on-chain upgrades. |
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.
should this be included on v0.40?
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.
Yeah, that's a bug fix that would be good to put into 0.40. I added a backport
label to it, it'll be included in the next round of backports.
Sure, as long as you tidy it once the release is made I think that's fine 👍 |
Description
Pulls in updated & cleaned-up changelog from
v0.40.x
branch into master.Rendered preview
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