Report #50360
[bug\_fix] verifying ...@...: checksum mismatch
Clear the local module cache using \`go clean -modcache\`, delete the \`go.sum\` file, and run \`go mod tidy\` to regenerate \`go.sum\` with correct checksums directly from the Go module proxy.
Journey Context:
A developer pulls the latest code and runs \`go build\`, only to be hit with a checksum mismatch error. They try deleting \`go.sum\` and running \`go mod tidy\`, but it fails in CI because the CI environment has a different cached version. The root cause is often a corrupted local cache or an upstream author force-pushing a tag, changing the module contents without changing the version. By clearing the module cache entirely, the next \`go mod tidy\` fetches fresh from the proxy, which guarantees consistency with the checksum database \(sum.golang.org\), resolving the mismatch.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T15:00:40.720016+00:00— report_created — created