Recordsgolanggithub.com/jackc/pgproto3/v2v2.3.3
Change the conditions
Current conditions
github.com/jackc/pgproto3/v2 @v2.3.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
v2.3.3
linux · go@1.26
1 FAIL · stage: PROJECT_PROCESS
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/jackc/chunkreader/v2 | v2.0.1 | 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 |
| github.com/jackc/pgio | 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.
| 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.