Recordsgolanggithub.com/jackc/pgx/v5v5.9.2
Change the conditions
Current conditions
github.com/jackc/pgx/v5 @v5.9.2windows · x64 · go 1.26 · go 1
package-level total, not an API
2 of 2 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
- 2 / 2
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-17
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 1. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/text | v0.29.0 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| github.com/jackc/pgpassfile | v1.0.0 | PASS All observations passed | contract passed | 1 project-day |
| github.com/jackc/pgservicefile | v0.0.0-20240606120523-5a60cdf6a761 | PASS All observations passed | contract passed | 1 project-day |
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.