CodeSampleX

Recordsgolanggithub.com/jackc/pgtypev1.14.4github.com/jackc/pgtype.Bool

Change the conditions
Fixed
OSubuntu glibc Symbolgithub.com/jackc/pgtype.Bool
Filter Runtimego 1.26 Package versionv1.14.4 Architecturex64 Package managergo 1 libcglibc Clear filters

Current conditions

github.com/jackc/pgtype.Bool @v1.14.4ubuntu glibc · x64 · go 1.26 · go 1

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-09-03

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 4 · Unknown 1 · Steady 2

First observed break

v1.14.4

linux · go@1.26 · executionContext=go

2 FAIL · stage: PROJECT_TEST

Library Version Health Measured there Projects
github.com/jackc/pgx/v4 v4.18.2 CANDIDATE Correlated change; unproven combination builds observed 8 project-days
github.com/lib/pq v1.10.2 CANDIDATE Correlated change; unproven combination nothing measured 8 project-days
github.com/shopspring/decimal v1.2.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 8 project-days
github.com/gofrs/uuid v4.0.0+incompatible UNKNOWN No linked outcome measured nothing measured 8 project-days
github.com/jackc/pgconn v1.14.3 PASS All observations passed contract passed 8 project-days
github.com/jackc/pgio v1.0.0 PASS All observations passed contract passed 8 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