Recordsgolanggo.opentelemetry.io/auto/sdkv1.2.1
Change the conditions
Current conditions
go.opentelemetry.io/auto/sdk @v1.2.1windows 11 · x64 · go (version not recorded) · go 1
package-level total, not an API
2 of 2 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 (1)
- Project observations
- 2 / 2
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-17
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.2.1
go@1.26
19 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/stretchr/testify | v1.11.1 | CANDIDATE Correlated change; unproven combination | contract passed | 82 project-days |
| github.com/stretchr/testify | v1.12.1 | CANDIDATE Correlated change; unproven combination | builds observed | 17 project-days |
| go.opentelemetry.io/otel | v1.43.0 | CANDIDATE Correlated change; unproven combination | contract passed | 59 project-days |
| go.opentelemetry.io/otel | v1.44.0 | CANDIDATE Correlated change; unproven combination | builds observed | 6 project-days |
| go.opentelemetry.io/otel | v1.45.0 | CANDIDATE Correlated change; unproven combination | contract passed | 22 project-days |
| go.opentelemetry.io/otel | v1.46.0 | CANDIDATE Correlated change; unproven combination | contract passed | 17 project-days |
| go.opentelemetry.io/otel/trace | v1.43.0 | CANDIDATE Correlated change; unproven combination | contract passed | 59 project-days |
| go.opentelemetry.io/otel/trace | v1.44.0 | CANDIDATE Correlated change; unproven combination | builds observed | 6 project-days |
| go.opentelemetry.io/otel/trace | v1.45.0 | CANDIDATE Correlated change; unproven combination | contract passed | 22 project-days |
| go.opentelemetry.io/otel/trace | v1.46.0 | CANDIDATE Correlated change; unproven combination | contract passed | 17 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.