Recordsgolanggo.opentelemetry.io/otel/trace
Change the conditions
Current conditions
go.opentelemetry.io/otel/trace @v1.39.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
- 8 / 8
- Contract verifications
- 3 / 3
- Usage records
- 4
- Independent reporting peers
- 1
- Last recorded
- 2026-10-11
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/trace.Link
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.39.0
linux · go@1.26
3 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:adde90373eac0c9660ca3dc55f78f4c7b34584ed07aaa1939d856cd3e880efe9
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/google/go-cmp | v0.7.0 | CANDIDATE Correlated change; unproven combination | contract passed | 18 project-days |
| github.com/stretchr/testify | v1.11.1 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| go.opentelemetry.io/otel | v1.39.0 | CANDIDATE Correlated change; unproven combination | builds observed | 18 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 | v1.47.0 | v1.46.0 | v1.45.0 | v1.44.0 | v1.43.0 | v1.39.0 | v1.38.0 | v1.37.0 | v1.36.0 | v1.35.0 | v1.34.0 | v1.28.0 | v1.24.0 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| github.com/google/go-cmp | v0.7.0 | v0.7.0 | v0.7.0 | v0.7.0 | v0.7.0 | v0.7.0 | v0.7.0 | v0.7.0 | v0.7.0 | v0.7.0 | v0.6.0 | — | v0.6.0 |
| github.com/stretchr/testify | v1.12.1 | v1.12.1 | v1.11.1 | v1.11.1 | v1.11.1 | v1.11.1 | — | v1.11.1 | v1.10.0 | v1.10.0 | — | — | v1.8.4 |
| go.opentelemetry.io/otel | v1.47.0 | v1.46.0 | v1.45.0 | v1.44.0 | v1.43.0 | v1.39.0 | v1.38.0 | v1.37.0 | v1.36.0 | v1.35.0 | v1.34.0 | v1.28.0 | v1.24.0 |
Moved: 3 · 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.