Recordsgolanggithub.com/jackc/pgproto3/v2v2.1.1github.com/jackc/pgproto3/v2.NewBackend
Change the conditions
Current conditions
github.com/jackc/pgproto3/v2.NewBackend @v2.1.1debian glibc · x64 · go 1.26 · go · go
1 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (1)
- Project observations
- 2 / 2
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-17
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v2.1.1
linux · go@1.26
2 FAIL
· stage: UNKNOWN
· fingerprint: sha256:48372bc6eceb6a0c62a2b1b8e31983a5160af2c1415fc01f5633712b77fac853
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/jackc/chunkreader/v2 | v2.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| github.com/jackc/chunkreader/v2 | v2.0.1 | CANDIDATE Correlated change; unproven combination | contract passed | 12 project-days |
| github.com/stretchr/testify | v1.4.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| github.com/stretchr/testify | v1.7.0 | CANDIDATE Correlated change; unproven combination | contract passed | 12 project-days |
| github.com/jackc/pgio | v1.0.0 | PASS All observations passed | contract passed | 15 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 | v2.3.3 | v2.1.1 |
|---|---|---|
| github.com/jackc/chunkreader/v2 | v2.0.1 | v2.0.0 |
| github.com/stretchr/testify | v1.8.1 | v1.4.0 |
| github.com/jackc/pgio | v1.0.0 | v1.0.0 |
Moved: 2 · unchanged at every release: 1
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.
Recent failure clusters
-
observed UNKNOWN exit 1 ERROR Evidence gap ×2 v2.1.1 os=linux · runtime=go@1.26 github.com/jackc/pgproto3/v2.NewBackend sha256:48372bc6eceb…go: downloading github.com/jackc/pgmock v0.0.0-20210724152146-4ad1a8207f65 · go: downloading github.<token> v2.0.1 …go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-14 · Last seen: 2026-09-14Diagnostic re-verification candidate
-
observed PROJECT_COMPILE exit 1 ×1 v2.1.1 os=linux · runtime=go@1.26 github.com/jackc/pgproto3/v2.NewBackend sha256:a0e1c511de91…test/contract.go:<n>:<n>: assignment mismatch: 2 variables but sm.Encode returns 1 value …go/compiler · compiler-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-14 · Last seen: 2026-09-14
-
observed PROJECT_COMPILE exit 1 ×1 v2.1.1 os=linux · runtime=go@1.26 github.com/jackc/pgproto3/v2.NewBackend sha256:fbcd3e8fd1fc…test/contract.go:<n>:<n>: undefined: pgproto3.AuthenticationResponsego/compiler · compiler-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-14 · Last seen: 2026-09-14
-
observed PROJECT_COMPILE exit 1 ×1 v2.1.1 os=linux · runtime=go@1.26 github.com/jackc/pgproto3/v2.NewBackend sha256:5dbb94925efc…<path> assignment mismatch: 2 variables but query.Encode returns 1 valuego/compiler · compiler-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-14 · Last seen: 2026-09-14