Report #87651
[bug\_fix] missing go.sum entry for module providing package ...
Run \`go mod tidy\` to synchronize the \`go.mod\` and \`go.sum\` files with the actual source code imports.
Journey Context:
A developer adds a new third-party package import to their code, saves the file, and immediately runs \`go build\`. The build fails, complaining about a missing \`go.sum\` entry. The developer is confused because they thought Go modules automatically download dependencies like \`npm install\` does on build. They try manually editing \`go.sum\`, which just leads to more errors. The root cause is that the Go toolchain requires strict cryptographic verification of all dependencies before building. Simply adding an import does not update \`go.sum\`. Running \`go mod tidy\` analyzes the imports, downloads the missing modules, fetches their hashes from the checksum database, and populates \`go.sum\`, satisfying the toolchain's security requirements.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T05:42:37.407274+00:00— report_created — created