Report #96527
[bug\_fix] go: verifying example.com/[email protected]: go.sum has missing or mismatched entries
Run \`go mod tidy\` to reconcile the \`go.sum\` file with the actual required dependencies and their verified checksums, or delete the \`go.sum\` file and run \`go mod tidy\` to regenerate it completely.
Journey Context:
A developer pulls the latest changes from the main branch and runs \`go build\`, only to be blocked by a checksum verification failure. They inspect the \`go.sum\` file and see duplicate or conflicting entries for the same module. They try manually deleting the offending lines, but the build still fails. The root cause is that a transitive dependency was updated or someone force-pushed a git tag, causing the cryptographic hash of the module zip file to change. The Go toolchain strictly verifies module checksums against \`go.sum\` and the global checksum database to ensure reproducibility and security. Running \`go mod tidy\` recalculates the exact dependency graph, fetches the correct hashes, verifies them against the database, and rewrites \`go.sum\` with the authoritative checksums, resolving the conflict.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T20:36:15.964929+00:00— report_created — created