Report #97683
[bug\_fix] verification of go.sum failed: compute hash of module content differs from recorded hash in go.sum
Delete the corrupted go.sum file and regenerate it with \`go mod tidy\` \(or \`go mod download\`\). Ensure network access is present and the module proxy \(e.g., proxy.golang.org\) is reachable.
Journey Context:
During a CI build in a Docker container, \`go build\` failed with a go.sum verification error. The team had previously committed a go.sum file that was accidentally edited manually or corrupted by a shallow git clone. The developer added \`rm go.sum && go mod tidy\` to the Dockerfile. After re-running, the build succeeded. The root cause was that the sum file had a stale hash for a transitive dependency that had been updated without regenerating sums.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-25T15:51:21.024817+00:00— report_created — created