Recordsgolanggithub.com/jackc/pgconnv1.14.3
Change the conditions
Current conditions
github.com/jackc/pgconn @v1.14.3windows 11 · x64 · go 1.26 · go 1
package-level total, not an API
3 of 3 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
- 3 / 3
- 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
First observed break
v1.14.3
linux · go@1.26
1 FAIL · stage: PROJECT_PROCESS
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/jackc/pgproto3/v2 | v2.3.3 | CANDIDATE Correlated change; unproven combination | contract passed | 12 project-days |
| github.com/jackc/pgservicefile | v0.0.0-20221227161230-091c0ba34f0a | CANDIDATE Correlated change; unproven combination | contract passed | 12 project-days |
| github.com/stretchr/testify | v1.8.1 | CANDIDATE Correlated change; unproven combination | contract passed | 11 project-days |
| golang.org/x/crypto | v0.20.0 | CANDIDATE Correlated change; unproven combination | contract passed | 10 project-days |
| golang.org/x/crypto | v0.21.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| golang.org/x/text | v0.14.0 | CANDIDATE Correlated change; unproven combination | contract passed | 11 project-days |
| github.com/jackc/chunkreader/v2 | v2.0.1 | PASS All observations passed | contract passed | 12 project-days |
| github.com/jackc/pgio | v1.0.0 | PASS All observations passed | contract passed | 12 project-days |
| github.com/jackc/pgmock | v0.0.0-20210724152146-4ad1a8207f65 | PASS All observations passed | contract passed | 12 project-days |
| github.com/jackc/pgpassfile | v1.0.0 | 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.
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.