Recordscargoyoke-derive
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
No recorded evidence matches these filters. Nothing is inferred; clear a filter to widen the slice.
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 | 3.0.6 | CHANGED Version changed, no linked failure | nothing measured | 33 project-days |
| synstructure | 0.14.0 | CHANGED Version changed, no linked failure | nothing measured | 33 project-days |
| proc-macro2 | 1.0.107 | PASS All observations passed | contract passed | 33 project-days |
| quote | 1.0.47 | PASS All observations passed | contract passed | 33 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.