Recordsgolanggithub.com/Masterminds/semver/v3failure issue
Failure signature
PROJECT_COMPILE exit 1 ×1
test/contract_test.go:<n>:<n>: assignment mismatch: 1 variable but c.Validate returns 2 values
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go test · First recorded: 2026-08-31 · Last seen: 2026-08-31
sha256:ea561eff281b…
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_COMPILE 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 ×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.3.0 → first failing release v3.5.0
Releases between them never measured at this stage: 1
One side of this boundary has no resolved dependency tree, so nothing could be compared.
Evidence gaps
- Releases in this window never measured at PROJECT_COMPILE: 2
- No resolved dependency tree for v3.3.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.