Repository navigation
Releases
@flakemetry/vitest-reporter@0.2.0
@flakemetry/sdk@0.3.0
@flakemetry/playwright-reporter@0.2.0
@flakemetry/jest-reporter@0.2.0
@flakemetry/core@0.2.0
@flakemetry/contracts@0.4.0
Minor Changes
- 4667bbd: Node 22.12 or later is now required, and each package declares it in
engines. Node 20 reached end-of-life in April 2026; the reporters are tested on Node 22.12 exactly.
@flakemetry/cli@0.3.0
@flakemetry/vitest-reporter@0.1.4
Patch Changes
-
b23f674: Sharded Jest and Vitest runs keep every shard. Each shard of one CI run used to get the same idempotency key, so the API kept the first shard and dropped the rest as re-deliveries. The reporters now pass the runner's
--shardto the SDK, and the SDK readsFLAKEMETRY_SHARD_INDEX/FLAKEMETRY_SHARD_TOTAL, which were documented but never read, for suites split some other way. -
2682df5: TypeScript projects that load these packages with
requirenow get CommonJS type declarations. Every package pointed bothimportandrequireat the ESM declaration file, so undermoduleResolution: node16a CommonJS consumer got types describing an ES module ("masquerading as ESM"). The files that run are unchanged. -
df69361: Installs and reports correctly on every Vitest from 1.6 to 5.
- The peer range was
^4.1.10, so npm refused the install withERESOLVEon Vitest 5, and on 1.6–3, which the reporter supported before a dependency sweep narrowed the range. It is now^1.6.0 || ^2.0.0 || ^3.0.0 || ^4.0.0 || ^5.0.0. - On Vitest 3, which calls both
onFinishedandonTestRunEnd, each run was delivered twice. Outside CI the two deliveries had different idempotency keys, so two runs were stored. A run is now delivered once, and each run of a watch session is still delivered.
- The peer range was
-
Updated dependencies [63cd348]
-
Updated dependencies [49cb6b1]
-
Updated dependencies [2d07cc2]
-
Updated dependencies [9cf5e92]
-
Updated dependencies [674ddb3]
-
Updated dependencies [cd50173]
-
Updated dependencies [b23f674]
-
Updated dependencies [cd52503]
-
Updated dependencies [2682df5]
-
Updated dependencies [eae093b]
- @flakemetry/contracts@0.3.0
- @flakemetry/sdk@0.2.3
@flakemetry/sdk@0.2.3
Patch Changes
- 49cb6b1: Dependency updates: OpenTelemetry 2.11 / 0.222 in the SDK, zod 4.6 in the contracts, and newer
yamlandfast-xml-parserin the CLI. - 2d07cc2: File paths are normalized by segment, so equivalent spellings of a path give one fingerprint.
/./tests/a.spec.ts,././tests/a.spec.ts,tests//a.spec.tsandtests/./a.spec.tsused to give different fingerprints, which could split one test's history across identities when it was reported through more than one route. Paths without such segments normalize exactly as before, so existing fingerprints do not change. - b23f674: Sharded Jest and Vitest runs keep every shard. Each shard of one CI run used to get the same idempotency key, so the API kept the first shard and dropped the rest as re-deliveries. The reporters now pass the runner's
--shardto the SDK, and the SDK readsFLAKEMETRY_SHARD_INDEX/FLAKEMETRY_SHARD_TOTAL, which were documented but never read, for suites split some other way. - 2682df5: TypeScript projects that load these packages with
requirenow get CommonJS type declarations. Every package pointed bothimportandrequireat the ESM declaration file, so undermoduleResolution: node16a CommonJS consumer got types describing an ES module ("masquerading as ESM"). The files that run are unchanged. - Updated dependencies [63cd348]
- Updated dependencies [49cb6b1]
- Updated dependencies [2d07cc2]
- Updated dependencies [9cf5e92]
- Updated dependencies [674ddb3]
- Updated dependencies [cd50173]
- Updated dependencies [cd52503]
- Updated dependencies [2682df5]
- Updated dependencies [eae093b]
- @flakemetry/contracts@0.3.0
- @flakemetry/core@0.1.3
@flakemetry/playwright-reporter@0.1.4
Patch Changes
- 55b17be: Installs on Playwright 1.44 and later again. A dependency update had narrowed the peer range to
^1.62.1, so npm refused the install on older Playwright releases, although the reporter works unchanged on them. It was checked on 1.44.1 and 1.63.0. - 2682df5: TypeScript projects that load these packages with
requirenow get CommonJS type declarations. Every package pointed bothimportandrequireat the ESM declaration file, so undermoduleResolution: node16a CommonJS consumer got types describing an ES module ("masquerading as ESM"). The files that run are unchanged. - Updated dependencies [63cd348]
- Updated dependencies [49cb6b1]
- Updated dependencies [2d07cc2]
- Updated dependencies [9cf5e92]
- Updated dependencies [674ddb3]
- Updated dependencies [cd50173]
- Updated dependencies [b23f674]
- Updated dependencies [cd52503]
- Updated dependencies [2682df5]
- Updated dependencies [eae093b]
- @flakemetry/contracts@0.3.0
- @flakemetry/sdk@0.2.3