CodeSampleX

Recordsgolanggithub.com/jackc/pgproto3/v2v2.3.3github.com/jackc/pgproto3/v2.Query

Change the conditions
Fixed
OSubuntu glibc Symbolgithub.com/jackc/pgproto3/v2.Query
Filter Runtimego 1.26 Package versionv2.3.3 Architecturex64 Package managergo 1 libcglibc Clear filters

Current conditions

github.com/jackc/pgproto3/v2.Query @v2.3.3ubuntu glibc · x64 · go 1.26 · go 1

3 of 3 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
3 / 3
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-08-26

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 1

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.

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