Recordsgolanggo.opentelemetry.io/otel/metric/xv0.68.0
Change the conditions
Current conditions
go.opentelemetry.io/otel/metric/x @v0.68.0debian glibc · x64 · go 1.26 · go · go
package-level total, not an API
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
- 4 / 4
- Contract verifications
- 1 / 1
- Usage records
- 7
- Independent reporting peers
- 1
- Last recorded
- 2026-09-17
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 2. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| go.opentelemetry.io/otel | v1.46.0 | CHANGED Version changed, no linked failure | contract passed | 13 project-days |
| go.opentelemetry.io/otel/metric | v1.46.0 | CHANGED Version changed, no linked failure | contract passed | 13 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 | v0.68.0 | v0.67.0 |
|---|---|---|
| go.opentelemetry.io/otel | v1.46.0 | v1.45.0 |
| go.opentelemetry.io/otel/metric | v1.46.0 | v1.45.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.