Recordsgolanggo.opentelemetry.io/otel/sdk/metricv1.37.0go.opentelemetry.io/otel/sdk/metric.Aggregation
Change the conditions
Current conditions
go.opentelemetry.io/otel/sdk/metric.Aggregation @v1.37.0linux · glibc · x64 · go 1.26 · go 1
0 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 failed (1)
- Project observations
- 1 / 1
- Contract verifications
- 0 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-17
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 8. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/go-logr/logr | v1.4.3 | CHANGED Version changed, no linked failure | contract passed | 29 project-days |
| github.com/google/go-cmp | v0.7.0 | CHANGED Version changed, no linked failure | contract passed | 29 project-days |
| github.com/stretchr/testify | v1.10.0 | CHANGED Version changed, no linked failure | builds observed | 19 project-days |
| github.com/stretchr/testify | v1.11.1 | CHANGED Version changed, no linked failure | contract passed | 5 project-days |
| go.opentelemetry.io/otel | v1.37.0 | CHANGED Version changed, no linked failure | contract passed | 29 project-days |
| go.opentelemetry.io/otel/metric | v1.37.0 | CHANGED Version changed, no linked failure | contract passed | 29 project-days |
| go.opentelemetry.io/otel/sdk | v1.37.0 | CHANGED Version changed, no linked failure | contract passed | 29 project-days |
| go.opentelemetry.io/otel/trace | v1.37.0 | CHANGED Version changed, no linked failure | contract passed | 29 project-days |
| github.com/go-logr/stdr | v1.2.2 | PASS All observations passed | contract passed | 29 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: 8 · unchanged at every release: 1
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.