Recordscargoyoke-derive0.8.2
Change the conditions
Current conditions
yoke-derive @0.8.2ubuntu glibc · x64 · cargo 1
package-level total, not an API
2 of 2 passed
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- 2 / 2
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-14
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 |
|---|---|---|---|---|
| syn | 2.0.119 | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| synstructure | 0.13.2 | CHANGED Version changed, no linked failure | builds observed | 3 project-days |
| proc-macro2 | 1.0.107 | PASS All observations passed | contract passed | 3 project-days |
| quote | 1.0.47 | PASS All observations passed | contract passed | 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.
| Library | 0.8.3 | 0.8.2 |
|---|---|---|
| syn | 3.0.6 | 2.0.119 |
| synstructure | 0.14.0 | 0.13.2 |
| proc-macro2 | 1.0.107 | 1.0.107 |
| quote | 1.0.47 | 1.0.47 |
Moved: 2 · 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.