Recordsgolanggo.opentelemetry.io/otel/sdkv1.45.0
Change the conditions
Current conditions
go.opentelemetry.io/otel/sdk @v1.45.0windows 11 · x64 · go 1.26 · go
package-level total, not an API
1 of 1 passed
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (12)
- Project observations
- 1 / 1
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-15
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.45.0
linux · go@1.26 · executionContext=go
6 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/go-logr/logr | v1.4.4 | 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/otel | v1.45.0 | CANDIDATE Correlated change; unproven combination | contract passed | 30 project-days |
| go.opentelemetry.io/otel/metric | v1.45.0 | CANDIDATE Correlated change; unproven combination | builds observed | 22 project-days |
| go.opentelemetry.io/otel/sdk/metric | v1.45.0 | CANDIDATE Correlated change; unproven combination | contract passed | 22 project-days |
| go.opentelemetry.io/otel/trace | v1.45.0 | CANDIDATE Correlated change; unproven combination | contract passed | 27 project-days |
| golang.org/x/sys | v0.47.0 | CANDIDATE Correlated change; unproven combination | contract passed | 22 project-days |
| github.com/google/uuid | v1.6.0 | PASS All observations passed | contract passed | 22 project-days |
| go.uber.org/goleak | v1.3.0 | PASS All observations passed | contract passed | 21 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: 8 · unchanged at every release: 2
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.