Recordsgolanggithub.com/cpuguy83/go-md2man/v2failure issue
Failure signature
PROJECT_TEST Evidence gap ×2
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-26 · Last seen: 2026-08-26
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- os=linux · runtime=go@1.26 ×2 2026-08-26 → 2026-08-26
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last failing release v2.0.2 → first passing release v2.0.6
Both trees resolved every dependency to the same version. Nothing here moved.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | v2.0.7 | v2.0.6 | v2.0.2 |
|---|---|---|---|
| github.com/russross/blackfriday/v2 | v2.1.0 | v2.1.0 | v2.1.0 |
Moved: 0 · unchanged at every release: 1
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/cpuguy83/go-md2man/v2 v2.0.2: md2man.Render 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. HOWmd2man.Rendergo 1.26.6 MIT-0 · 2026-08-28