Recordsgolanggithub.com/envoyproxy/go-control-plane/envoyv1.32.2github.com/envoyproxy/go-control-plane/envoy/config/core/v3.Address
Change the conditions
Current conditions
github.com/envoyproxy/go-control-plane/envoy/config/core/v3.Address @v1.32.2ubuntu glibc · x64 · go 1.26 · go 1
2 of 2 passed
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- 2 / 2
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-10-15
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 8. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/cncf/xds/go | v0.0.0-20240723142845-024c85f92f20 | CHANGED Version changed, no linked failure | builds observed | 8 project-days |
| github.com/envoyproxy/protoc-gen-validate | v1.1.0 | CHANGED Version changed, no linked failure | builds observed | 8 project-days |
| github.com/prometheus/client_model | v0.6.0 | CHANGED Version changed, no linked failure | nothing measured | 8 project-days |
| go.opentelemetry.io/proto/otlp | v1.0.0 | CHANGED Version changed, no linked failure | nothing measured | 8 project-days |
| google.golang.org/genproto/googleapis/api | v0.0.0-20240814211410-ddb44dafa142 | CHANGED Version changed, no linked failure | nothing measured | 8 project-days |
| google.golang.org/genproto/googleapis/rpc | v0.0.0-20240814211410-ddb44dafa142 | CHANGED Version changed, no linked failure | builds observed | 8 project-days |
| google.golang.org/grpc | v1.67.1 | CHANGED Version changed, no linked failure | contract passed | 8 project-days |
| google.golang.org/protobuf | v1.35.2 | CHANGED Version changed, no linked failure | contract passed | 8 project-days |
| github.com/planetscale/vtprotobuf | v0.6.1-0.20240319094008-0393e58bdf10 | 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: 8 · unchanged at every release: 2
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.