Recordsgolanggithub.com/googleapis/gax-go/v2v2.23.0gax.XGoogHeader
Change the conditions
Current conditions
gax.XGoogHeader @v2.23.0debian glibc · x64 · go 1.26 · go · go
1 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (1)
- Project observations
- 2 / 2
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-10-10
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 16. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/google/go-cmp | v0.7.0 | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| go.opentelemetry.io/otel | v1.44.0 | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| go.opentelemetry.io/otel/metric | v1.44.0 | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| go.opentelemetry.io/otel/sdk/metric | v1.44.0 | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| google.golang.org/api | v0.287.1 | CHANGED Version changed, no linked failure | contract passed | 2 project-days |
| google.golang.org/api | v0.293.0 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| google.golang.org/genproto | v0.0.0-20260319201613-d00831a3d3e7 | CHANGED Version changed, no linked failure | builds observed | 3 project-days |
| google.golang.org/genproto/googleapis/api | v0.0.0-20260630182238-925bb5da69e7 | CHANGED Version changed, no linked failure | contract passed | 2 project-days |
| google.golang.org/genproto/googleapis/api | v0.0.0-20260706201446-f0a921348800 | CHANGED Version changed, no linked failure | builds observed | 1 project-day |
| google.golang.org/genproto/googleapis/rpc | v0.0.0-20260630182238-925bb5da69e7 | CHANGED Version changed, no linked failure | contract passed | 2 project-days |
| google.golang.org/genproto/googleapis/rpc | v0.0.0-20260807164820-c8921c73eeea | CHANGED Version changed, no linked failure | builds observed | 1 project-day |
| google.golang.org/grpc | v1.82.0 | CHANGED Version changed, no linked failure | builds observed | 1 project-day |
| google.golang.org/grpc | v1.83.2 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| google.golang.org/grpc | v1.84.0 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| google.golang.org/protobuf | v1.36.11 | CHANGED Version changed, no linked failure | contract passed | 2 project-days |
| google.golang.org/protobuf | v1.36.12 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
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: 10 · 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.