CodeSampleX

Recordsgolanggithub.com/cncf/xds/go

Compatibility cube

Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.

Fixed
Runtimego@1.26 Package versionv0.0.0-20251110193048-8bfbf64dc13e

No recorded evidence matches these filters. Nothing is inferred; clear a filter to widen the slice.

The cube reads the newest 6 versions and the first 10 symbols of each, so an empty cell here can mean "outside that window" rather than "never measured".

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 9 · Steady 0

First observed break

v0.0.0-20251110193048-8bfbf64dc13e

linux · go@1.26

1 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:4b2b0e15a2f05affcf6c094626a7238844f891e10f924b91c6645e069ae831d7

Library Version Health Measured there Projects
cel.dev/expr v0.24.0 CANDIDATE Correlated change; unproven combination contract passed 32 project-days
github.com/envoyproxy/protoc-gen-validate v1.2.1 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
github.com/envoyproxy/protoc-gen-validate v1.3.0 CANDIDATE Correlated change; unproven combination builds observed 31 project-days
google.golang.org/genproto/googleapis/api v0.0.0-20240903143218-8af14fe29dc1 CANDIDATE Correlated change; unproven combination nothing measured 1 project-day
google.golang.org/genproto/googleapis/api v0.0.0-20251029180050-ab9386a59fda CANDIDATE Correlated change; unproven combination contract passed 31 project-days
google.golang.org/grpc v1.68.0 CANDIDATE Correlated change; unproven combination nothing measured 1 project-day
google.golang.org/grpc v1.78.0 CANDIDATE Correlated change; unproven combination contract passed 31 project-days
google.golang.org/protobuf v1.36.10 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
google.golang.org/protobuf v1.36.11 CANDIDATE Correlated change; unproven combination contract passed 31 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: 5 · unchanged at every release: 0

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.