CodeSampleX

Recordsgolanggo.opentelemetry.io/auto/sdkv1.2.1

Change the conditions
Fixed
OSubuntu glibc Package managernpm 10
Filter Runtimenode 22 Package versionv1.2.1 Symbolwhole package Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

go.opentelemetry.io/auto/sdk @v1.2.1ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 52 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed (1)

Project observations
38 / 39
Contract verifications
0 / 52
Usage records
145
Independent reporting peers
3
Last recorded
2026-09-08

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 10 · Steady 0

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.

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.

Recent failure clusters

Showing the 12 most-reported of 26 recorded failure clusters. The rest are single reports.