Recordsgolangcel.dev/exprv0.24.0cel.dev/expr.Expr
Change the conditions
Current conditions
cel.dev/expr.Expr @v0.24.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-09-17
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 4. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| google.golang.org/genproto/googleapis/rpc | v0.0.0-20240826202546-f6391c0de4c7 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| google.golang.org/genproto/googleapis/rpc | v0.0.0-20250728155136-f173205681a0 | CHANGED Version changed, no linked failure | contract passed | 8 project-days |
| google.golang.org/protobuf | v1.34.2 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| google.golang.org/protobuf | v1.36.10 | CHANGED Version changed, no linked failure | 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.
| 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.