Recordsgolanggo.opentelemetry.io/auto/sdk
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
No recorded evidence matches these filters. Nothing is inferred; clear a filter to widen the slice.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.1.0
go@1.26
19 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/stretchr/testify | v1.10.0 | CANDIDATE Correlated change; unproven combination | builds observed | 40 project-days |
| github.com/stretchr/testify | v1.11.1 | CANDIDATE Correlated change; unproven combination | contract passed | 6 project-days |
| go.opentelemetry.io/otel | v1.34.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| go.opentelemetry.io/otel | v1.35.0 | CANDIDATE Correlated change; unproven combination | contract passed | 7 project-days |
| go.opentelemetry.io/otel | v1.37.0 | CANDIDATE Correlated change; unproven combination | contract passed | 44 project-days |
| go.opentelemetry.io/otel/trace | v1.34.0 | CANDIDATE Correlated change; unproven combination | builds observed | 3 project-days |
| go.opentelemetry.io/otel/trace | v1.35.0 | CANDIDATE Correlated change; unproven combination | contract passed | 7 project-days |
| go.opentelemetry.io/otel/trace | v1.37.0 | CANDIDATE Correlated change; unproven combination | contract passed | 44 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.2.1 | v1.1.0 |
|---|---|---|
| github.com/stretchr/testify | v1.12.1 | v1.11.1 |
| go.opentelemetry.io/otel | v1.44.0 | v1.34.0 |
| go.opentelemetry.io/otel/trace | v1.44.0 | v1.34.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.