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

[Bug]: feegrant relies on cosmossdk.io/core v0.12.0 but sdk-rc.1 relies on cosmossdk.io/core v0.11.0 #17950

Closed
1 task done
jtieri opened this issue Oct 3, 2023 · 1 comment
Labels

Comments

@jtieri
Copy link
Member

jtieri commented Oct 3, 2023

Is there an existing issue for this?

  • I have searched the existing issues

What happened?

I'm currently working on upgrading the go-relayer to sdk v0.50.0-rc.1 and noticed that after accounting for all breaking changes and trying to compile I get the following errors:

# github.com/cosmos/cosmos-sdk/types
../../../../pkg/mod/github.com/cosmos/[email protected]/types/context.go:64:29: undefined: comet.BlockInfo
../../../../pkg/mod/github.com/cosmos/[email protected]/types/context.go:91:36: undefined: comet.BlockInfo
../../../../pkg/mod/github.com/cosmos/[email protected]/types/context.go:299:48: undefined: comet.BlockInfo
make: *** [install] Error 1

I saw in my indirect dependencies that cosmossdk.io/core v0.12.0 is being imported but the latest rc of sdk v0.50.0 relies on cosmossdk.io/core v0.11.0. After doing some digging I realized that v0.12.0 is imported because the go-relayer also imports cosmossdk.io/x/feegrant.

comet.BlockInfo was renamed to comet.Info from v0.11.0 -> v0.12.0 so the Go module system complains because when two deps with the same major revision are needed it defaults to the most recent version.

I was curious if there were plans to upgrade this dependency in sdk 0.50.0 in the next release candidate?

Additionally I was wondering if there were plans to create tags for the feegrant module because right now it's one of the modules that are its own Go module but there are not explicit tags being created for it so you have to rely on a commit sha

Cosmos SDK Version

0.50.0-rc.1

How to reproduce?

Import cosmos sdk v0.50.0-rc.1 along with the latest commit sha from the feegrant module then try to compile the code that is importing both dependencies.

@jtieri jtieri added the T:Bug label Oct 3, 2023
@julienrbrt
Copy link
Member

It will be clearer once we tag the modules, but you need to take the latest commit of the release branch.
x/feegrant on the release/v0.50.x imports the correct version of core that is compatible with v0.50 (https://github.com/cosmos/cosmos-sdk/blob/release/v0.50.x/x/feegrant/go.mod#L7).

All modules that import the SDK are tagged from release branches (see https://github.com/cosmos/cosmos-sdk/blob/main/RELEASE_PROCESS.md#cosmos-sdk-modules)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants