Report #11484
[bug\_fix] go: [email protected]: missing go.sum entry; to add it: go mod tidy
Run \`go mod tidy\` to synchronize the \`go.mod\` and \`go.sum\` files, fetching missing modules and recording their cryptographic checksums.
Journey Context:
A developer adds a new third-party import to their code, saves the file, and immediately runs \`go build\`. The build fails with a "missing go.sum entry" error. The developer might try to manually copy-paste a hash into \`go.sum\` from a colleague's branch, which leads to further "checksum mismatch" errors. The root cause is that the Go module system requires cryptographic checksums of all direct and indirect dependencies in \`go.sum\` for reproducible, verified builds. Since the import was just added, the local toolchain hasn't fetched the module or calculated its hash yet. Running \`go mod tidy\` automatically resolves all imports, downloads missing modules, and populates \`go.sum\` with the correct checksums from the global checksum database \(sum.golang.org\), ensuring the supply chain remains intact.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T13:23:51.808937+00:00— report_created — created