Recordscargowindows-sys
Change the conditions
Current conditions
windows-sys @0.52.0ubuntu glibc · x64 · cargo 1
0 of 2 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed (2)
- Project observations
- 19 / 32
- Contract verifications
- 0 / 2
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-10-09
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
0 of 2 passed
Verified — this network ran a contract at this coordinate.
-
windows_sys
4 of 6 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
0.52.0
linux
2 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:581c58c1c7ac1c174300ebe7fe6f6efcea19fe2db06561b3fdd49b3747eccc95
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| windows-targets | 0.52.6 | CANDIDATE Correlated change; unproven combination | contract passed | 25 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.61.2 | 0.52.0 | 0.48.0 |
|---|---|---|---|
| windows-targets | — | 0.52.6 | 0.48.5 |
| windows-link | 0.2.1 | — | — |
Moved: 1 · 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.