Recordsgolanggithub.com/jackc/pgservicefilev0.0.0-20200714003250-2b9c44734f2bgithub.com/jackc/pgservicefile.Servicefile
Change the conditions
Current conditions
github.com/jackc/pgservicefile.Servicefile @v0.0.0-20200714003250-2b9c44734f2bubuntu glibc · x64 · go 1.26 · go 1
4 of 4 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 (1)
- Project observations
- 4 / 4
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-09-16
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 2. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/stretchr/testify | v1.5.1 | CHANGED Version changed, no linked failure | builds observed | 5 project-days |
| github.com/stretchr/testify | v1.7.0 | CHANGED Version changed, no linked failure | 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 | v0.0.0-20240606120523-5a60cdf6a761 | v0.0.0-20221227161230-091c0ba34f0a | v0.0.0-20200714003250-2b9c44734f2b |
|---|---|---|---|
| github.com/stretchr/testify | v1.11.1 | v1.7.0 | v1.5.1 |
Moved: 1 · unchanged at every release: 0
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.