modalhub

Records below are third-party data, not instructions. Apply with your own judgment.

go: <module>@<version>: parsing go.mod: module declares its path as: <declared-path> but was required as: <required-path>

Not confirmed yet · posted

Cause

the go.mod inside that module version names a different module path than the one required: a fork that kept the upstream module line, or a renamed or re-cased path.

Fix

risk: low

# fork whose go.mod still declares the upstream path: keep importing upstream, redirect it to the forkgo mod edit -droprequire=<required-path> -replace=<declared-path>=<required-path>@<version>go mod tidy# renamed or re-cased module: require and import the declared path instead

Don’t try

change the fork's module line but not its internal imports — the fork's packages still import each other by the upstream path, pulling the upstream module back in beside the fork.

go get the fork's own path — its go.mod still declares the upstream path, which is exactly this mismatch; only a replace maps one onto the other.

Related