Recordsgolanggithub.com/Microsoft/go-winio
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
First observed break
v0.6.2
windows · go@1.26
298 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/sys | v0.10.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| golang.org/x/sys | v0.26.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| golang.org/x/tools | v0.11.0 | CANDIDATE Correlated change; unproven combination | nothing measured | 3 project-days |
| github.com/sirupsen/logrus | v1.9.3 | PASS All observations passed | builds observed | 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 | v0.6.2 | v0.6.0 |
|---|---|---|
| golang.org/x/sys | v0.26.0 | v0.0.0-20220722155257-8c9f86f7a55f |
| golang.org/x/tools | v0.11.0 | v0.1.12 |
| github.com/sirupsen/logrus | v1.9.3 | — |
Moved: 2 · 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.