Report #58967
[bug\_fix] verifying go.mod: missing go.sum entry for module ...
Run \`go mod tidy\` to recalculate and populate the \`go.sum\` file with the required cryptographic hashes, then commit the updated \`go.sum\`.
Journey Context:
A developer pulls the latest changes from the main branch and runs \`go build\`. The build fails with a verification error. They might try deleting \`go.sum\` and running \`go build\` again, which temporarily works but is destructive and loses hashes of indirect dependencies. They might also try manually adding the hash, which is error-prone. The root cause is that a teammate added a new dependency or updated one in \`go.mod\` but forgot to commit the corresponding \`go.sum\` file, or a transitive dependency was updated. \`go mod tidy\` is the canonical way to synchronize \`go.mod\` and \`go.sum\` with the actual imports, ensuring the \`go.sum\` contains the correct verified hashes for all dependencies.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T05:27:59.997228+00:00— report_created — created