Recordsgolanggithub.com/jackc/pgconnv1.9.0
Change the conditions
Current conditions
github.com/jackc/pgconn @v1.9.0debian glibc · x64 · go 1.26 · go · go
package-level total, not an API
Recorded as present in projects. Nothing was run at this coordinate.
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- nothing at this coordinate
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-14
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 5. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/jackc/pgproto3/v2 | v2.1.1 | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| github.com/jackc/pgservicefile | v0.0.0-20200714003250-2b9c44734f2b | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| github.com/stretchr/testify | v1.7.0 | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| golang.org/x/crypto | v0.0.0-20210711020723-a769d52b0f97 | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| golang.org/x/text | v0.3.6 | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| github.com/jackc/chunkreader/v2 | v2.0.1 | PASS All observations passed | contract passed | 3 project-days |
| github.com/jackc/pgio | v1.0.0 | PASS All observations passed | contract passed | 3 project-days |
| github.com/jackc/pgmock | v0.0.0-20210724152146-4ad1a8207f65 | PASS All observations passed | contract passed | 3 project-days |
| github.com/jackc/pgpassfile | v1.0.0 | PASS All observations passed | contract passed | 3 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: 5 · unchanged at every release: 4
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.