CodeSampleX

Compatibilitynpmjest29.6.3getVersion

Change the conditions
Fixed
OSubuntu glibc SymbolgetVersion
Filter Runtimenode 22 Package version29.6.3 Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

getVersion @29.6.3ubuntu glibc · x64 · node 22 · npm 10 · node

0 of 4 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed (1)

Project observations
2 / 2
Contract verifications
0 / 4
Independent reporting peers
1
Last recorded
2026-08-31
Evidence you can open

Dependencies

LibraryVersionMeasured thereProjects
@jest/core 29.6.3 builds observed 2 project-days
@jest/core 29.7.0 contract passed 3 project-days
@jest/types 29.6.3 contract passed 3 project-days
import-local 3.2.0 contract passed 3 project-days
jest-cli 29.6.3 nothing measured 1 project-day
jest-cli 29.7.0 contract passed 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.

Library30.4.229.7.029.6.3
@jest/core 30.4.2 29.7.0 29.6.3
@jest/types 30.4.1 29.6.3 29.6.3
jest-cli 30.4.2 29.7.0 29.6.3
import-local 3.2.0 3.2.0 3.2.0

Moved: 3 · 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.

Recent failure clusters