Skip to content

v0.2.10 — vitest 5.0.1 fix

Choose a tag to compare

View all tags
@jaypetez jaypetez released this 21 Sep 21:36
· 4 commits to main since this release
v0.2.10
7a6b765
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Completes the dependency maintenance batch from 0.2.9: vitest/@vitest/coverage-v8 5.0.0 → 5.0.1, held back at the time after CI showed apps/web typecheck failures.

Changed

  • Dev tooling: vitest/@vitest/coverage-v8 5.0.0 → 5.0.1.

    The earlier failure was not a vitest regression — @vitest/expect's Assertion type declaration is byte-identical between 5.0.0 and 5.0.1 (diffed the packed npm tarballs directly). The real cause: Dependabot's frozen lockfile snapshot resolved two different @types/node versions across the two peer-qualified vitest@5.0.1 variants in the workspace, so @testing-library/jest-dom's vitest type augmentation landed on a different physical vitest instance than the one apps/web's test files actually imported. Re-resolving the lockfile converges both variants onto a single @types/node and fixes it, with no version pin changes beyond the intended bump.

Full changelog: v0.2.9...v0.2.10

Assets 2
Loading