Update vitest 3.2.2 → 3.2.4 (patch) #2040
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ vitest (3.2.2 → 3.2.4) · Repo
Release Notes
3.2.4
3.2.3
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 36 commits:
chore: release v3.2.4
fix(runner): preserve handler wrapping on extend (#8153)
fix(browser): show a helpful error when spying on an export (#8178)
fix(cli): throw error when `--shard x/<count>` exceeds count of test files (#8112)
chore(deps): update `tinypool` (#8174)
docs: fix typos in documentation: "replaying" and "infering" (#8176)
fix(deps): update all non-major dependencies (#8123)
chore(deps): update dependency @antfu/ni to v25 (#8166)
chore(deps): update dependency @vitejs/plugin-basic-ssl to v2 (#8167)
chore: configure vscode extensions (#8163)
fix(coverage): ignore SCSS in browser mode (#8161)
docs: Typo in doc for `watchTriggerPatterns` (#8157)
test: flaky test-run timing (#8150)
fix(expect): handle async errors in expect.soft (#8145)
chore: update deprecation notice for globs (#8148)
ci: use Nodejs 24 (#7999)
chore: update deprecated workspace file log (#8118)
fix(pool): auto-adjust `minWorkers` when only `maxWorkers` specified (#8110)
fix(cli): use absolute path environment on Windows (#8105)
fix(reporter): `task.meta` should be available in custom reporter's errors (#8115)
fix(ui): ensure ui config option works correctly (#8147)
fix(cli): `vitest run --watch` should be watch-mode (#8128)
docs: capitalize titles (#8143)
fix: print uint and buffer as a simple string (#8141)
fix: use correct path for optimisation of strip-literal (#8139)
docs(coverage): small typos (#8113)
chore: release v3.2.3
fix: run only the name plugin last, not all config plugins (#8130)
fix: revert `expect.any` return type (#8129)
fix(vite-node): unable to handle errors where sourcemap mapping empty (#8071)
fix(runner): comments between fixture destructures (#8127)
fix(runner): fast sequential task updates missing (#8121)
feat(browser): use base url instead of __vitest__ (#8126)
fix(pool): throw if user's tests use `process.send()` (#8125)
feat(ui): show test annotations and metadata in the test report tab (#8093)
fix: rerun tests when project's setup file is changed (#8097)
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands