Recordsnpmjest-circus30.4.2
Change the conditions
Current conditions
jest-circus @30.4.2ubuntu glibc · x64 · node 22 · npm 10 · node
package-level total, not an API
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
- Project observations
- 4 / 4
- Contract verifications
- 0 / 2
- Independent reporting peers
- 1
- Last recorded
- 2026-08-31
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| @jest/environment | 30.4.1 | contract passed | 2 project-days |
| @jest/expect | 30.4.1 | contract passed | 2 project-days |
| @jest/test-result | 30.4.1 | contract passed | 2 project-days |
| @jest/types | 30.4.1 | contract passed | 2 project-days |
| @types/node | 26.4.0 | contract passed | 2 project-days |
| chalk | 4.1.2 | contract passed | 2 project-days |
| co | 4.6.0 | contract passed | 2 project-days |
| dedent | 1.7.2 | contract passed | 2 project-days |
| is-generator-fn | 2.1.0 | contract passed | 2 project-days |
| jest-each | 30.4.1 | contract passed | 2 project-days |
| jest-matcher-utils | 30.4.1 | contract passed | 2 project-days |
| jest-message-util | 30.4.1 | contract passed | 2 project-days |
| jest-runtime | 30.4.2 | contract passed | 2 project-days |
| jest-snapshot | 30.4.1 | contract passed | 2 project-days |
| jest-util | 30.4.1 | contract passed | 2 project-days |
| p-limit | 3.1.0 | contract passed | 2 project-days |
| pretty-format | 30.4.1 | contract passed | 2 project-days |
| pure-rand | 7.0.1 | contract passed | 2 project-days |
| slash | 3.0.0 | contract passed | 2 project-days |
| stack-utils | 2.0.6 | contract passed | 2 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 | 30.4.2 | 29.7.0 |
|---|---|---|
| @jest/environment | 30.4.1 | 29.7.0 |
| @jest/expect | 30.4.1 | 29.7.0 |
| @jest/test-result | 30.4.1 | 29.7.0 |
| @jest/types | 30.4.1 | 29.6.3 |
| @types/node | 26.4.0 | 26.2.0 |
| jest-each | 30.4.1 | 29.7.0 |
| jest-matcher-utils | 30.4.1 | 29.7.0 |
| jest-message-util | 30.4.1 | 29.7.0 |
| jest-runtime | 30.4.2 | 29.7.0 |
| jest-snapshot | 30.4.1 | 29.7.0 |
| jest-util | 30.4.1 | 29.7.0 |
| pretty-format | 30.4.1 | 29.7.0 |
| pure-rand | 7.0.1 | 6.1.0 |
| chalk | 4.1.2 | 4.1.2 |
| co | 4.6.0 | 4.6.0 |
| dedent | 1.7.2 | 1.7.2 |
| is-generator-fn | 2.1.0 | 2.1.0 |
| p-limit | 3.1.0 | 3.1.0 |
| slash | 3.0.0 | 3.0.0 |
| stack-utils | 2.0.6 | 2.0.6 |
Moved: 13 · unchanged at every release: 7
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 UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 30.4.2 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:054c93088b95…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ …node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 30.4.2 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:a878372dcfe9…AssertionError [ERR_ASSERTION]: getVersion must return 30.4.2 · <str> !== <str> · at main (<path>:<n>:<n>) · at Object.<anonymous> (<path>:<n>:<n>)node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate