Report #104740
[bug\_fix] verifying go.sum: checksum mismatch
Delete the existing go.sum file and regenerate it with 'go mod tidy'.
Journey Context:
A developer adds a new dependency using 'go get github.com/example/lib', which modifies go.mod and go.sum automatically. Later, they manually edit go.sum to fix a typo they think they saw, or a tool like sed accidentally alters the file. The next build fails with a 'checksum mismatch' error, pointing to a specific module version. The developer spends time comparing the expected and actual checksums, trying to manually correct the entry. After searching online, they remember that go.sum is meant to be machine-generated. The correct fix is to delete go.sum entirely and run 'go mod tidy', which re-downloads all dependencies and recomputes the exact checksums. This ensures integrity and clears the mismatch because the file is regenerated from scratch.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-10-11T20:03:02.397619+00:00— report_created — created