Recordsgolanggo.opentelemetry.io/otel
Change the conditions
Current conditions
go.opentelemetry.io/otel @v1.42.0debian glibc · x64 · go 1.26 · go · go
3 of 3 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 (3)
- Project observations
- 4 / 4
- Contract verifications
- 3 / 3
- Usage records
- 5
- Independent reporting peers
- 1
- Last recorded
- 2026-10-13
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
3 of 3 passed
Verified — this network ran a contract at this coordinate.
-
go.opentelemetry.io/otel.ErrorHandlerFunc
1 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.42.0
linux · go@1.26
5 FAIL
· stage: UNKNOWN
· fingerprint: sha256:042f6e977a16262a7e633b3137ce9291be598b66496d9201e447ee2b8efa6eb8
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/go-logr/logr | v1.4.3 | CANDIDATE Correlated change; unproven combination | contract passed | 22 project-days |
| github.com/google/go-cmp | v0.7.0 | CANDIDATE Correlated change; unproven combination | contract passed | 22 project-days |
| github.com/stretchr/testify | v1.11.1 | CANDIDATE Correlated change; unproven combination | contract passed | 22 project-days |
| go.opentelemetry.io/auto/sdk | v1.2.1 | CANDIDATE Correlated change; unproven combination | contract passed | 22 project-days |
| go.opentelemetry.io/otel/metric | v1.42.0 | CANDIDATE Correlated change; unproven combination | contract passed | 22 project-days |
| go.opentelemetry.io/otel/trace | v1.42.0 | CANDIDATE Correlated change; unproven combination | contract passed | 22 project-days |
| github.com/cespare/xxhash/v2 | v2.3.0 | PASS All observations passed | contract passed | 22 project-days |
| github.com/go-logr/stdr | v1.2.2 | PASS All observations passed | contract passed | 22 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: 3
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.