Records/golang/github.com/dustin/go-humanize/failure issue

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.

• v1.0.1 FAIL
• v1.0.0 PASS 4 passing observations

Where it reproduced

• os=windows · 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 passing release v1.0.0 → first failing release v1.0.1

  Both trees resolved every dependency to the same version. Nothing here moved.

Evidence gaps

• No failure domain was inferred for this failure.

Published answers for the affected releases

• github.com/dustin/go-humanize v1.0.1: FormatInteger and FormatFloat format string patterns require an explicit trailing decimal delimiter to suppress fractional digits and apply thousands grouping Built ? 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. HOWhumanize.FormatIntegerhumanize.FormatFloatgo MIT-0 · 2026-08-19
• github.com/dustin/go-humanize v1.0.1: format byte sizes and numbers with dustin go-humanize Built ? 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-08-18