Recordsgolanggo.opentelemetry.io/otel/metricv1.37.0go.opentelemetry.io/otel/metric.MeterConfig
Change the conditions
Current conditions
go.opentelemetry.io/otel/metric.MeterConfig @v1.37.0linux · glibc · x64 · go 1.26 · go · go
1 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (1)
- Project observations
- 2 / 2
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-17
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.37.0
linux · go@1.26
5 FAIL
· stage: UNKNOWN
· fingerprint: sha256:042f6e977a16262a7e633b3137ce9291be598b66496d9201e447ee2b8efa6eb8
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/stretchr/testify | v1.10.0 | CANDIDATE Correlated change; unproven combination | builds observed | 32 project-days |
| github.com/stretchr/testify | v1.11.1 | CANDIDATE Correlated change; unproven combination | contract passed | 6 project-days |
| go.opentelemetry.io/otel | v1.37.0 | CANDIDATE Correlated change; unproven combination | contract passed | 43 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.46.0 | v1.45.0 | v1.44.0 | v1.43.0 | v1.37.0 | v1.35.0 | v1.34.0 | v1.28.0 | v1.24.0 |
|---|---|---|---|---|---|---|---|---|---|
| github.com/stretchr/testify | v1.12.1 | v1.11.1 | v1.11.1 | v1.11.1 | v1.11.1 | v1.10.0 | — | — | v1.8.4 |
| go.opentelemetry.io/otel | v1.46.0 | v1.45.0 | v1.44.0 | v1.43.0 | v1.37.0 | v1.35.0 | v1.34.0 | v1.28.0 | v1.24.0 |
Moved: 2 · 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
-
observed UNKNOWN exit 1 Evidence gap ×5 v1.37.0 → v1.43.0 os=linux · runtime=go@1.26 go.opentelemetry.io/otel/metric.MeterConfig sha256:042f6e977a16…go: updates to go.mod needed; to update it: · go mod tidygo · unclassified-diagnostic · outer go run, go test · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-09-16Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v1.37.0 os=linux · runtime=go@1.26 go.opentelemetry.io/otel/metric.MeterConfig sha256:61579858e38a…# sample/test · test/contract.go:<n>:<n>: cannot call pointer method Len on <str>.Set · test/contract.go:<n>:<n>: cannot call pointer method Len on <str>.Setgo · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-16 · Last seen: 2026-09-16Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v1.37.0 os=linux · runtime=go@1.26 sha256:93a520b5395d…# command-line-arguments · <path> cannot call pointer method Len on <str>.Set · <path> cannot call pointer method Len on <str>.Setgo · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-16 · Last seen: 2026-09-16Diagnostic re-verification candidate