Recordsgolanggo.opentelemetry.io/otel/tracev1.42.0
Change the conditions
Current conditions
go.opentelemetry.io/otel/trace @v1.42.0debian glibc · x64 · go 1.26 · go · go
package-level total, not an API
4 of 4 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 (4)
- Project observations
- 4 / 4
- Contract verifications
- 4 / 4
- Usage records
- 4
- Independent reporting peers
- 1
- Last recorded
- 2026-10-12
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 3. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/google/go-cmp | v0.7.0 | CHANGED Version changed, no linked failure | contract passed | 6 project-days |
| github.com/stretchr/testify | v1.11.1 | CHANGED Version changed, no linked failure | contract passed | 6 project-days |
| go.opentelemetry.io/otel | v1.42.0 | CHANGED Version changed, no linked failure | contract passed | 6 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.42.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.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.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.42.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.