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

Bump Cosmos-SDK to v0.41 #566

Closed
Jelena647 opened this issue Jan 25, 2021 · 1 comment · Fixed by #579
Closed

Bump Cosmos-SDK to v0.41 #566

Jelena647 opened this issue Jan 25, 2021 · 1 comment · Fixed by #579
Assignees

Comments

@Jelena647
Copy link
Contributor

Jelena647 commented Jan 25, 2021

Note that it's currently listed as Milestone v0.40.2 since v0.41 contains lots of other planned work but since the changes from #568 are breaking v0.40.2 will need to be v0.41 and what was previously v0.41 will be v0.42 - https://github.com/cosmos/cosmos-sdk/milestone/37 - should be updated in the SDK milestones @ clevinson @aaronc

@Jelena647 Jelena647 changed the title SDK Release Cosmos-SDK amino support Jan 25, 2021
@Jelena647 Jelena647 changed the title Cosmos-SDK amino support Cosmos-SDK amino json support Jan 25, 2021
@shahankhatch shahankhatch changed the title Cosmos-SDK amino json support Bump Cosmos-SDK to v0.42.0 Jan 25, 2021
@shahankhatch shahankhatch changed the title Bump Cosmos-SDK to v0.42.0 Bump Cosmos-SDK to v0.40.2 Jan 25, 2021
@ebuchman ebuchman changed the title Bump Cosmos-SDK to v0.40.2 Bump Cosmos-SDK to v0.41 Jan 25, 2021
@aaronc
Copy link
Member

aaronc commented Jan 25, 2021

Thanks @Jelena647. The SDK release team has not yet made this decision regarding versioning. I know others have proposed it but we currently aren't thinking in this direction. We will share our thoughts in a public channel.

@shahankhatch shahankhatch linked a pull request Jan 26, 2021 that will close this issue
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 a pull request may close this issue.

3 participants