Recordsgolanggithub.com/jackc/pgx/v5
Change the conditions
Current conditions
github.com/jackc/pgx/v5 @v5.7.6ubuntu glibc · x64 · go 1.26 · go 1
8 of 8 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 (2)
- Project observations
- 8 / 8
- Contract verifications
- nothing at this coordinate
- Usage records
- 8
- Independent reporting peers
- 2
- Last recorded
- 2026-09-10
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
8 of 8 passed
Observed — real project builds reported from this coordinate.
-
github.com/jackc/pgx/v5.ParseConfig
8 of 8 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 4. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/stretchr/testify | v1.8.1 | CHANGED Version changed, no linked failure | contract passed | 2 project-days |
| golang.org/x/crypto | v0.37.0 | CHANGED Version changed, no linked failure | builds observed | 2 project-days |
| golang.org/x/sync | v0.13.0 | CHANGED Version changed, no linked failure | nothing measured | 2 project-days |
| golang.org/x/text | v0.24.0 | CHANGED Version changed, no linked failure | builds observed | 2 project-days |
| github.com/jackc/pgpassfile | v1.0.0 | PASS All observations passed | contract passed | 2 project-days |
| github.com/jackc/pgservicefile | v0.0.0-20240606120523-5a60cdf6a761 | PASS All observations passed | contract passed | 2 project-days |
| github.com/jackc/puddle/v2 | v2.2.2 | PASS All observations passed | contract passed | 2 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.
Moved: 4 · unchanged at every release: 3
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.