Recordscargosyn3.0.10
Change the conditions
Current conditions
syn @3.0.10alpine musl · x64 · rust 1 · cargo · rust
package-level total, not an API
Recorded as present in projects. Nothing was run at this coordinate.
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- nothing at this coordinate
- Contract verifications
- nothing at this coordinate
- Usage records
- 2
- Independent reporting peers
- 1
- Last recorded
- 2026-11-17
Dependency Health
Observed combinations and failure evidence for this release
First observed break
3.0.10
linux
5 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:0479254218ac3780b34745e946705b5f6ea072bc45cc7771f5a9b6fbfb5955e8
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| unicode-ident | 1.0.27 | CANDIDATE Correlated change; unproven combination | contract passed | 18 project-days |
| proc-macro2 | 1.0.107 | PASS All observations passed | contract passed | 18 project-days |
| quote | 1.0.47 | PASS All observations passed | contract passed | 18 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 | 3.0.10 | 3.0.9 | 3.0.7 | 3.0.6 | 3.0.5 | 3.0.3 | 2.0.119 |
|---|---|---|---|---|---|---|---|
| unicode-ident | 1.0.27 | 1.0.27 | 1.0.26 | 1.0.25 | 1.0.25 | 1.0.26 | 1.0.25 |
| proc-macro2 | 1.0.107 | 1.0.107 | 1.0.107 | 1.0.107 | 1.0.107 | 1.0.107 | 1.0.107 |
| quote | 1.0.47 | 1.0.47 | 1.0.47 | 1.0.47 | 1.0.47 | 1.0.47 | 1.0.47 |
Moved: 1 · 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.
Recent failure clusters
-
observed PROJECT_COMPILE exit 101 E0308 ×5 3.0.5 → 3.0.6 → 3.0.9 → 3.0.10 os=linux sha256:0479254218ac…error[E0308]: mismatched typesrust/rustc · compiler-diagnostic · outer cargo run, cargo testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-16 · Last seen: 2026-11-17
-
observed PROJECT_COMPILE exit 101 ×4 2.0.119 → 3.0.10 os=linux sha256:6e60e3f6eb26…error: could not compile `verify-axum-macros-from-request` (bin <str>) due to 1 previous errorrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-17 · Last seen: 2026-11-17
-
observed PROJECT_COMPILE exit 101 ×2 2.0.119 → 3.0.10 os=linux sha256:16ffdf41a116…error: could not compile `sample-axum-macros-debug-middleware` (bin <str>) due to 1 previous errorrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-17 · Last seen: 2026-11-17
-
observed PROJECT_COMPILE exit 101 ×2 2.0.119 → 3.0.10 os=linux sha256:255d33c441d5…error: could not compile `verify-axum-macros-from-request` (bin <str>) due to 6 previous errorsrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-17 · Last seen: 2026-11-17
-
observed PROJECT_COMPILE exit 101 E0284 ×2 2.0.119 → 3.0.10 os=linux sha256:28ce80525d69…error[E0284]: type annotations neededrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-17 · Last seen: 2026-11-17
-
observed PROJECT_COMPILE exit 101 E0277 ×2 2.0.119 → 3.0.10 os=linux sha256:4a23cd1a3b5d…error[E0277]: the trait bound `Trimmed<TrimmedNote>: FromRequest<()>` is not satisfiedrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-17 · Last seen: 2026-11-17
-
observed PROJECT_COMPILE exit 101 E0599 ×2 2.0.119 → 3.0.10 os=linux sha256:60101c049b0d…error[E0599]: the associated function or constant `from_request` exists for struct `TrimmedNote`, but its trait bounds were not satisfiedrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-17 · Last seen: 2026-11-17
-
observed PROJECT_COMPILE exit 101 E0425 ×2 2.0.119 → 3.0.10 os=linux sha256:9afa67c05dca…error[E0425]: cannot find function `__axum_macros_check_describe_into_response_check` in this scope …rust/rustc · compiler-diagnostic · outer cargo buildEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-17 · Last seen: 2026-11-17
-
observed PROJECT_COMPILE exit 101 ×2 2.0.119 → 3.0.10 os=linux sha256:b0b78cd39ba8…error: could not compile `sample-axum-macros-debug-handler` (lib) due to 2 previous errors; 2 warnings emittedrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-17 · Last seen: 2026-11-17
-
observed PROJECT_COMPILE exit 101 E0599 ×2 2.0.119 → 3.0.10 os=linux sha256:c512f6091afa…error[E0599]: the associated function or constant `from_request` exists for struct `ViaState`, but its trait bounds were not satisfiedrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-17 · Last seen: 2026-11-17
-
observed PROJECT_COMPILE exit 101 ×2 2.0.119 → 3.0.10 os=linux sha256:c75eb1372c32…error: could not compile `verify-axum-macros-from-request` (bin <str>) due to 3 previous errorsrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-17 · Last seen: 2026-11-17
-
observed PROJECT_COMPILE exit 101 E0277 ×2 2.0.119 → 3.0.10 os=linux sha256:d3d2c06814df…error[E0277]: the trait bound `CustomRejection: From<Infallible>` is not satisfied …rust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-17 · Last seen: 2026-11-17
Showing the 12 most-reported of 22 recorded failure clusters. The rest are single reports.