Report #63868
[bug\_fix] missing go.sum entry for module providing package
Run \`go mod tidy\` to synchronize the \`go.mod\` file with the actual imports in the codebase and populate \`go.sum\` with the cryptographic hashes of all required modules.
Journey Context:
A developer pulls the latest changes from their team's Git repository and runs \`go build\`. The build fails, complaining about a missing \`go.sum\` entry. They assume \`go.sum\` is just a lockfile and try to manually copy a hash from a colleague or run \`go mod download\`. The error persists. They go down a rabbit hole checking their \`GOPROXY\` settings and network connection, thinking the download failed silently. Finally, they realize that \`go.sum\` is not just a lockfile but a cryptographic verification mechanism \(using SHA256\) to ensure reproducibility and supply-chain security. \`go mod download\` only caches the module; it doesn't update \`go.sum\` if the dependency graph has changed. The fix is to run \`go mod tidy\`. This command reconciles the dependency state, calculates the cryptographic hashes of all required modules, and correctly populates \`go.sum\`. This works because \`go mod tidy\` is the canonical way to ensure the verifier has the exact hashes it needs for the current build.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T13:41:31.680342+00:00— report_created — created