build: Bump jest and @types/jest - #25
Conversation
🔍 Lore Spec ImpactExamined 4 changed file(s): 0 had graph data (no coupling found), 4 had none — no ingested test run covers them, so this check cannot speak for them. Deterministic · graph baseline unknown (no ingested test run has stamped this repo) — line-precise coupling skipped · no tests run by this check |
f316ba3 to
16bf9e7
Compare
|
@dependabot rebase |
|
Looks like this PR is already up-to-date with main! If you'd still like to recreate it from scratch, overwriting any edits, you can request |
Bumps [jest](https://github.com/jestjs/jest/tree/HEAD/packages/jest) and [@types/jest](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/jest). These dependencies needed to be updated together. Updates `jest` from 29.7.0 to 30.5.1 - [Release notes](https://github.com/jestjs/jest/releases) - [Changelog](https://github.com/jestjs/jest/blob/main/CHANGELOG.md) - [Commits](https://github.com/jestjs/jest/commits/v30.5.1/packages/jest) Updates `@types/jest` from 29.5.14 to 30.0.0 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/jest) --- updated-dependencies: - dependency-name: "@types/jest" dependency-version: 30.0.0 dependency-type: direct:development update-type: version-update:semver-major - dependency-name: jest dependency-version: 30.5.1 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
c8f3ea3 to
15e713a
Compare
|
Added one commit so this can go green: All 385 tests passed on this branch already — the job failed only on two coverage floors, and only
Jest 30 instruments branch points jest 29 never saw. Not one branch that was covered became uncovered — the denominator grew by 123 while coverage grew by 92. So a group whose percentage fell did so because it gained branch points, not because it lost a test. Three floors rise (vertex 69.23 → 74.64, mock 75 → 78.57, global 59.42 → 64.82) and two fall (orchestration 85.91 → 80.85, tools 57.14 → 56.25). Net, the ratchet tightens. Two floors moving down would normally be exactly what the ratchet exists to stop, so
|
Jest 30 instruments branch points jest 29 never saw, so every branch floor is read by a different instrument than the one that set it. Across src/ the branch count goes 240/350 covered to 332/473, while statements (665/842), functions (180/226) and lines (601/756) are identical to the unit - the same 385 tests, none added, none removed. No branch that was covered became uncovered. A group whose percentage fell did so because its denominator grew: vertex 69.23 -> 74.64, mock 75 -> 78.57 and global 59.42 -> 64.82 rise, while orchestration 85.91 -> 80.85 and its tools 57.14 -> 56.25 fall. Three floors tighten and two loosen, which is the finer instrument reading the same suite rather than coverage being lost. AGENTS.md gains the case, because the rule it states - a floor that moves down is a regression with the alarm switched off - is otherwise contradicted here with nothing to say why. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LwoztdBKudtfu3JJkfamWx
Bumps jest and @types/jest. These dependencies needed to be updated together.
Updates
jestfrom 29.7.0 to 30.5.1Release notes
Sourced from jest's releases.
... (truncated)
Changelog
Sourced from jest's changelog.
... (truncated)
Commits
9ab14fev30.5.1912baa3v30.5.0b91717achore: refresh coding agent instructions (#16182)746f2a0v30.4.2b3b4a09v30.4.15cbb21ev30.4.0db7141afix: allowcollectCoverageandcoverageProviderin project config (#16132)efb59c2v30.3.096c53d3feat(jest-config): adddefineConfigandmergeConfigfunctions (#15844)855864ev30.2.0Updates
@types/jestfrom 29.5.14 to 30.0.0Commits