Recordsgolangcel.dev/exprv0.25.1
Change the conditions
Current conditions
cel.dev/expr @v0.25.1ubuntu glibc · x64 · go 1.26 · go 1
package-level total, not an API
0 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 failed
- Project observations
- 3 / 3
- Contract verifications
- 0 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-27
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.
Recent failure clusters
-
observed UNKNOWN exit 1 Evidence gap ×1 v0.25.1 os=linux · runtime=go@1.26 sha256:f3a5a3011077…panic: interface conversion: interface {} is nil, not *caddy.Replacer · goroutine 1 [running]: …go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-27 · Last seen: 2026-08-27Diagnostic re-verification candidate