Recordsnpm@jest/schemas29.6.3
Change the conditions
Current conditions
@jest/schemas @29.6.3windows 11 · x64 · node 24 · npm 11 · node
package-level total, not an API
1 of 1 passed
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (3)
- Project observations
- 1 / 1
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-18
Dependency Health
Observed combinations and failure evidence for this release
First observed break
29.6.3
linux · node@22.23 · executionContext=node
6 FAIL · stage: PROJECT_PROCESS
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @sinclair/typebox | 0.27.12 | CANDIDATE Correlated change; unproven combination | contract passed | 47 project-days |
| @sinclair/typebox | 0.27.8 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
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 | 30.4.1 | 29.6.3 |
|---|---|---|
| @sinclair/typebox | 0.34.52 | 0.27.8 |
Moved: 1 · unchanged at every release: 0
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.