CodeSampleX

Recordsgolanggithub.com/envoyproxy/go-control-planev0.9.0github.com/envoyproxy/go-control-plane/pkg/cache.IDHash

Change the conditions
Fixed
Symbolgithub.com/envoyproxy/go-control-plane/pkg/cache.IDHash
Filter OSubuntu glibc Runtimego 1.26 Package versionv0.9.0 Architecturex64 Package managergo 1 libcglibc Clear filters

Current conditions

github.com/envoyproxy/go-control-plane/pkg/cache.IDHash @v0.9.0ubuntu glibc · x64 · go 1.26 · go 1

2 of 3 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
2 / 3
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-10-16

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 6 · Unknown 1 · Steady 0

First observed break

v0.9.0

linux · go@1.26

1 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:93c0544f95070bc3255f1d95e255529c6d26786c01cc7213f3187a4fa44104ce

Library Version Health Measured there Projects
github.com/envoyproxy/protoc-gen-validate v0.1.0 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
github.com/golang/protobuf v1.3.2 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
github.com/prometheus/client_model v0.0.0-20190812154241-14fe0d1b01d4 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
google.golang.org/genproto v0.0.0-20190819201941-24fa4b261c55 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
google.golang.org/grpc v1.23.0 CANDIDATE Correlated change; unproven combination builds observed 1 project-day
google.golang.org/grpc v1.25.1 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
github.com/census-instrumentation/opencensus-proto v0.2.1 UNKNOWN No linked outcome measured nothing measured 7 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: 6 · unchanged at every release: 8

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