Report #5684
[bug\_fix] go: verifying go.sum: missing go.sum entry for ...
Run go mod tidy to recalculate and add the missing cryptographic checksums to go.sum, then commit the updated file.
Journey Context:
A developer pulls the latest code, adds a new import, and runs go build. It fails with "missing go.sum entry". They try go build again and it works \(because the first run added it to go.sum\), but their CI pipeline fails with the same error. They dive into a rabbit hole of manually editing go.sum or deleting it entirely, which leads to checksum mismatch errors. The root cause is that CI pipelines often use go build -mod=readonly or go mod verify to ensure reproducibility and security. If a dependency is added or changed in go.mod or source code without the corresponding hash being added to go.sum, the build tool refuses to download or verify it in read-only mode. go mod tidy synchronizes the go.sum file with the exact dependencies required by the code, generating the correct hashes.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T21:52:05.175297+00:00— report_created — created