Recordsgolangcloud.google.com/go/bigqueryv1.8.0
Change the conditions
Current conditions
cloud.google.com/go/bigquery @v1.8.0debian glibc · x64 · go 1.26 · go · go
package-level total, not an API
Recorded as present in projects. Nothing was run at this coordinate.
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- nothing at this coordinate
- Contract verifications
- nothing at this coordinate
- Usage records
- 6
- Independent reporting peers
- 1
- Last recorded
- 2026-10-09
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 |
|---|---|---|---|---|
| cloud.google.com/go | v0.57.0 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| cloud.google.com/go | v0.62.0 | CHANGED Version changed, no linked failure | builds observed | 4 project-days |
| cloud.google.com/go | v0.65.0 | CHANGED Version changed, no linked failure | contract passed | 5 project-days |
| cloud.google.com/go/storage | v1.10.0 | CHANGED Version changed, no linked failure | contract passed | 10 project-days |
| github.com/golang/protobuf | v1.4.2 | CHANGED Version changed, no linked failure | contract passed | 6 project-days |
| github.com/golang/protobuf | v1.5.0 | CHANGED Version changed, no linked failure | contract passed | 2 project-days |
| github.com/golang/protobuf | v1.5.2 | CHANGED Version changed, no linked failure | contract passed | 2 project-days |
| github.com/google/go-cmp | v0.4.1 | CHANGED Version changed, no linked failure | builds observed | 1 project-day |
| github.com/google/go-cmp | v0.5.1 | CHANGED Version changed, no linked failure | builds observed | 5 project-days |
| github.com/google/go-cmp | v0.5.5 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| github.com/google/go-cmp | v0.7.0 | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| google.golang.org/genproto | v0.0.0-20200618031413-b414f8b61790 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| google.golang.org/genproto | v0.0.0-20200804131852-c06518451d9c | CHANGED Version changed, no linked failure | builds observed | 4 project-days |
| google.golang.org/genproto | v0.0.0-20200825200019-8632dd797987 | CHANGED Version changed, no linked failure | builds observed | 5 project-days |
| google.golang.org/grpc | v1.29.1 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| google.golang.org/grpc | v1.31.0 | CHANGED Version changed, no linked failure | builds observed | 9 project-days |
| github.com/googleapis/gax-go/v2 | v2.0.5 | PASS All observations passed | contract passed | 10 project-days |
| google.golang.org/api | v0.28.0 | PASS All observations passed | contract passed | 1 project-day |
| google.golang.org/api | v0.30.0 | PASS All observations passed | contract passed | 9 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: 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.