Recordsgolanggithub.com/letsencrypt/pebble/v2failure issue
Failure signature
PROJECT_RESOLVE exit 1 ×1
<path>:<n>:<n>: missing go.sum entry for module providing package github.com/go-jose/go-jose/v4 (imported by github.<token>); to add: …
Evidence quality: complete · go/module · resolve-diagnostic · outer go list · First recorded: 2026-10-19 · Last seen: 2026-10-19
sha256:0abf71f153e5…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_RESOLVE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- v2.10.0 FAIL
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-10-19 → 2026-10-19
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
Evidence gaps
- No release in this window recorded a passing observation at PROJECT_RESOLVE.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/letsencrypt/pebble/v2 v2.10.0 This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW MIT-0 · 2026-10-19