Recordsgolanggithub.com/Masterminds/semver/v3failure issue
Failure signature
PROJECT_TEST exit 1 ×1
--- FAIL: TestVersionIncrementMethods (0.00s) · contract_test.go:<n>: expected IncPatch() to yield <str>, got <str> · FAIL example.com/sample/test 0.003s
Evidence quality: complete · go/test · test-runner-diagnostic · outer go test · First recorded: 2026-08-31 · Last seen: 2026-08-31
sha256:c94ceee121c8…
github.com/Masterminds/semver/v3.Collection github.com/Masterminds/semver/v3.NewConstraint github.com/Masterminds/semver/v3.NewVersion github.com/Masterminds/semver/v3.StrictNewVersion github.com/Masterminds/semver/v3.Version
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.
- v3.5.0 FAIL
- v3.4.0 PASS 2 passing observations
- v3.3.0 PASS 16 passing observations
- v3.2.0 PASS 6 passing observations
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-08-31 → 2026-08-31
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 v3.4.0 → first failing release v3.5.0
One side of this boundary has no resolved dependency tree, so nothing could be compared.
Evidence gaps
- No resolved dependency tree for v3.4.0 or for v3.5.0, so the versions either side of the boundary could not be compared.
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.