You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
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:
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 oncosmossdk.io/core v0.11.0
. After doing some digging I realized that v0.12.0 is imported because the go-relayer also importscosmossdk.io/x/feegrant
.comet.BlockInfo
was renamed tocomet.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.
The text was updated successfully, but these errors were encountered: