Recordsgolanggithub.com/spf13/castv1.10.0
Change the conditions
Current conditions
github.com/spf13/cast @v1.10.0windows 11 · x64 · go 1.26 · go 1
package-level total, not an API
1 of 1 passed
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (8)
- Project observations
- 1 / 1
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-14
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.10.0
linux · go@1.26
1 FAIL
· stage: PROJECT_TEST
· fingerprint: sha256:505fcd91bbc7ae091d2c7fe05998fe8c21822c1a66c7a729492f91f209a80aa6
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/frankban/quicktest | v1.14.6 | PASS All observations passed | contract passed | 12 project-days |
The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.
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 | v1.10.0 | v1.7.0 | v1.4.1 | v1.3.1 |
|---|---|---|---|---|
| github.com/stretchr/testify | — | — | v1.9.0 | v1.2.2 |
| github.com/frankban/quicktest | v1.14.6 | v1.14.6 | — | — |
Moved: 1 · 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.