Report #70421
[bug\_fix] go: verifying go.sum: missing or invalid checksum
Run \`go mod tidy\` to synchronize the \`go.sum\` file with the actual dependencies in \`go.mod\`, or delete \`go.sum\` and run \`go mod tidy\` to regenerate it.
Journey Context:
A developer pulls the latest code from version control and runs \`go build\`, only to be blocked by a checksum verification error. They might try manually editing \`go.sum\` or deleting specific lines, but the error persists or changes. The root cause is that the \`go.sum\` file is out of sync—perhaps a teammate added a dependency to \`go.mod\` without committing the updated \`go.sum\`, or a dependency was fetched from a different proxy with a different version or hash. The Go toolchain strictly verifies checksums for security and reproducibility, comparing the downloaded module against the hashes in \`go.sum\` and the global checksum database. \`go mod tidy\` recalculates the exact hashes required by the current \`go.mod\`, downloads any missing ones, and updates \`go.sum\`, restoring the cryptographic chain of trust.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T00:47:10.310622+00:00— report_created — created