Recordsgolanggithub.com/jackc/pgtypev1.14.0github.com/jackc/pgtype.JSONB
Change the conditions
Current conditions
github.com/jackc/pgtype.JSONB @v1.14.0ubuntu glibc · x64 · go 1.26 · go 1
1 of 1 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
- 1 / 1
- 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
First observed break
v1.14.0
linux · go@1.26 · executionContext=go
2 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/jackc/pgx/v4 | v4.12.1-0.20210724153913-640aa07df17c | CANDIDATE Correlated change; unproven combination | builds observed | 8 project-days |
| github.com/jackc/pgx/v4 | v4.18.3 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| github.com/lib/pq | v1.10.2 | CANDIDATE Correlated change; unproven combination | nothing measured | 12 project-days |
| github.com/shopspring/decimal | v1.2.0 | CANDIDATE Correlated change; unproven combination | contract passed | 11 project-days |
| github.com/stretchr/testify | v1.7.0 | CANDIDATE Correlated change; unproven combination | contract passed | 8 project-days |
| github.com/stretchr/testify | v1.8.1 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| github.com/gofrs/uuid | v4.0.0+incompatible | UNKNOWN No linked outcome measured | nothing measured | 12 project-days |
| github.com/jackc/pgconn | v1.14.3 | PASS All observations passed | contract passed | 4 project-days |
| github.com/jackc/pgconn | v1.9.1-0.20210724152538-d89c8390a530 | PASS All observations passed | builds observed | 8 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: 4 · unchanged at every release: 5
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 PROJECT_TEST Evidence gap ×2 v1.14.0 → v1.14.4 executionContext=go · os=linux · runtime=go@1.26Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-09-07 · Last seen: 2026-09-07Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v1.14.0 os=linux · runtime=go@1.26 sha256:48312c939afd…# sample · <path> unknown field Host in struct literal of type pgx.ConnConfig · <path> unknown field Port in struct literal of type pgx.ConnConfig …go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-30Diagnostic re-verification candidate