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

Update sdk version to v0.46.0-alpha2 #909

Closed
3 tasks
sahith-narahari opened this issue Feb 11, 2022 · 4 comments
Closed
3 tasks

Update sdk version to v0.46.0-alpha2 #909

sahith-narahari opened this issue Feb 11, 2022 · 4 comments
Assignees
Labels
dependencies Issues or PRs to update a dependency

Comments

@sahith-narahari
Copy link

Summary

We're testing out some recently added functionality on sdk, which needs a simapp with ibc. Is there a tracking issue or plan wrt sdk version upgrade? A branch with version updated would work, in case the team isn't comfortable cutting a release with alpha versions.
Here's a link to the sdk tag https://github.com/cosmos/cosmos-sdk/releases/tag/v0.46.0-alpha2

Problem Definition

Proposal

Create a branch or release which is compatible with v0.46-alpha2 of cosmos-sdk


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged/assigned
@sahith-narahari sahith-narahari changed the title Update sdk version to v0.46.2-alpha2 Update sdk version to v0.46.0-alpha2 Feb 11, 2022
@crodriguezvega
Copy link
Contributor

Thanks for opening this issue, @sahith-narahari.

Yes, we will plan and work on the upgrade to SDK 0.46. And yes, we will probably create a branch to start the integration but not release until the final version of the SDK is out.

@crodriguezvega crodriguezvega added the dependencies Issues or PRs to update a dependency label Feb 15, 2022
@faddat
Copy link
Contributor

faddat commented Feb 16, 2022

that's great news!

We're using 46 for craft economy :)

@faddat
Copy link
Contributor

faddat commented Feb 21, 2022

Hey, I've got a question about this-- the main challenge seems to be the upgrades to gov, and I realize that I can use the wrappers in v1beta2 to use the old gov v1beta1 types but as I've gone through it, I have been taking out support for v1beta1 and adding messages and the like for v 1beta2.

Can anyone tell me if this is right or wrong, and if I am tossing out compatibility by doing this?

@crodriguezvega
Copy link
Contributor

We have this branch now with 0.46-beta2 and this branch with 0.46-rc1. Please note that the former is the main branch for the work to upgrade to 0.46; the latter is a branch to make the incremental upgrade before the final release of 0.46 easier.

CosmosCar pushed a commit to caelus-labs/ibc-go that referenced this issue Nov 6, 2023
…ot exists (cosmos#909)

fixes cosmos#897

Co-authored-by: Ganesha Upadhyaya <gupadhyaya@Ganeshas-MacBook-Pro-2.local>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Issues or PRs to update a dependency
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants