Recordsgolangcel.dev/expr
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
No recorded evidence matches these filters. Nothing is inferred; clear a filter to widen the slice.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.25.1
linux · go@1.26
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:f3a5a30110770e510159fdb2eda104f320d4f31f36251c1770da6e4ec58af6d8
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| google.golang.org/protobuf | v1.36.11 | CANDIDATE Correlated change; unproven combination | contract passed | 2 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.
| Library | v0.25.1 | v0.24.0 | v0.19.1 |
|---|---|---|---|
| google.golang.org/genproto/googleapis/rpc | — | v0.0.0-20240826202546-f6391c0de4c7 | v0.0.0-20241007155032-5fefd90f89a9 |
| google.golang.org/protobuf | v1.36.11 | v1.34.2 | v1.35.1 |
Moved: 2 · 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.