Symptoms
go get or go mod tidy fails on a pseudo-version like v0.0.7-0.20190626134135-aca080dccfc2.
Causes
- Version prefix (e.g.
v0.0.7) doesn’t match any real tag in the upstream repo - Upstream history was rewritten / force-pushed, invalidating the
go.sumhash - Module proxy cached a broken state
- MVS picked a conflicting pseudo-version from a transitive dep
Fix
Remove the bad entries from go.mod and go.sum, then re-fetch with a valid anchor:
go get "github.com/some/module@v0.2.1-0.20190802003216-436d707f7cd0"This gives the resolver a clean, proxy-verifiable pseudo-version and drops the corrupted pin.