Recordsgolanggithub.com/jackc/pgx/v4
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
No recorded evidence matches these filters. Nothing is inferred; clear a filter to widen the slice.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v4.18.3
linux · go@1.26
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:48312c939afd34c0b5de0f8a0359d9d2ddb695696f2df444ffacd5609e104791
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/jackc/pgconn | v1.14.3 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| github.com/jackc/pgproto3/v2 | v2.3.3 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| github.com/jackc/pgtype | v1.14.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| github.com/jackc/puddle | v1.3.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| github.com/shopspring/decimal | v1.2.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| github.com/stretchr/testify | v1.8.1 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| go.uber.org/zap | v1.13.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| github.com/Masterminds/semver/v3 | v3.1.1 | UNKNOWN No linked outcome measured | nothing measured | 3 project-days |
| github.com/cockroachdb/apd | v1.1.0 | UNKNOWN No linked outcome measured | nothing measured | 3 project-days |
| github.com/gofrs/uuid | v4.0.0+incompatible | UNKNOWN No linked outcome measured | nothing measured | 3 project-days |
| gopkg.in/inconshreveable/log15.v2 | v2.0.0-20180818164646-67afb5ed74ec | UNKNOWN No linked outcome measured | nothing measured | 3 project-days |
| github.com/go-kit/log | v0.1.0 | 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/rs/zerolog | v1.15.0 | PASS All observations passed | contract passed | 3 project-days |
| github.com/sirupsen/logrus | v1.4.2 | 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: 7 · unchanged at every release: 10
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.