CodeSampleX

Recordsgolanggo.opentelemetry.io/otel/logv1.47.0go.opentelemetry.io/otel/log.Logger

Change the conditions
Fixed
OSubuntu glibc Package versionv1.47.0 Symbolgo.opentelemetry.io/otel/log.Logger
Filter Runtimego 1.26 Architecturex64 Package managergo 1 libcglibc Clear filters

Current conditions

go.opentelemetry.io/otel/log.Logger @v1.47.0ubuntu glibc · x64 · go 1.26 · go 1

1 of 1 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
1 / 1
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-10-10

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 1

First observed break

v1.47.0

linux · go@1.26

1 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:947b5eb5acb22df3e2b467a63ac602c8f2404752e554dadc9e0ac8d207dfca37

Library Version Health Measured there Projects
go.opentelemetry.io/otel v1.47.0 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
github.com/stretchr/testify v1.12.1 PASS All observations passed builds observed 3 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: 1 · 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.

Recent failure clusters