Recordscargoh20.4.20
Change the conditions
Current conditions
h2 @0.4.20ubuntu glibc · x64 · cargo 1
package-level total, not an API
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-19
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 |
|---|---|---|---|---|
| tokio | 1.54.0 | CHANGED Version changed, no linked failure | builds observed | 2 project-days |
| tokio-util | 0.7.20 | CHANGED Version changed, no linked failure | builds observed | 2 project-days |
| atomic-waker | 1.1.2 | PASS All observations passed | builds observed | 2 project-days |
| bytes | 1.12.1 | PASS All observations passed | contract passed | 2 project-days |
| fnv | 1.0.7 | PASS All observations passed | builds observed | 2 project-days |
| futures-core | 0.3.34 | PASS All observations passed | contract passed | 2 project-days |
| futures-sink | 0.3.34 | PASS All observations passed | contract passed | 2 project-days |
| http | 1.5.0 | PASS All observations passed | contract passed | 2 project-days |
| indexmap | 2.14.2 | PASS All observations passed | builds observed | 2 project-days |
| slab | 0.4.12 | PASS All observations passed | contract passed | 2 project-days |
| tracing | 0.1.44 | PASS All observations passed | contract passed | 2 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 | 0.4.20 | 0.4.19 |
|---|---|---|
| tokio | 1.54.0 | 1.53.1 |
| tokio-util | 0.7.20 | 0.7.19 |
| atomic-waker | 1.1.2 | 1.1.2 |
| bytes | 1.12.1 | 1.12.1 |
| fnv | 1.0.7 | 1.0.7 |
| futures-core | 0.3.34 | 0.3.34 |
| futures-sink | 0.3.34 | 0.3.34 |
| http | 1.5.0 | 1.5.0 |
| indexmap | 2.14.2 | 2.14.2 |
| slab | 0.4.12 | 0.4.12 |
| tracing | 0.1.44 | 0.1.44 |
Moved: 2 · unchanged at every release: 9
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.