Recordsgolangcloud.google.com/go/bigqueryv1.0.1
Change the conditions
Current conditions
cloud.google.com/go/bigquery @v1.0.1debian 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
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-10-18
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 6. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| cloud.google.com/go | v0.46.3 | CHANGED Version changed, no linked failure | contract passed | 5 project-days |
| github.com/golang/protobuf | v1.3.2 | CHANGED Version changed, no linked failure | contract passed | 5 project-days |
| github.com/google/go-cmp | v0.3.0 | CHANGED Version changed, no linked failure | contract passed | 5 project-days |
| google.golang.org/api | v0.14.0 | CHANGED Version changed, no linked failure | contract passed | 5 project-days |
| google.golang.org/genproto | v0.0.0-20191115194625-c23dd37a84c9 | CHANGED Version changed, no linked failure | contract passed | 5 project-days |
| google.golang.org/grpc | v1.21.1 | CHANGED Version changed, no linked failure | contract passed | 5 project-days |
| github.com/googleapis/gax-go/v2 | v2.0.5 | PASS All observations passed | contract passed | 5 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: 7 · unchanged at every release: 1
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.