what stackpulse tracks
Vitest releases from GitHub
StackPulse watches Vitest release notes and keeps the original source link close to every summary.
#stacks/vitest/testing
Vitest release notes, breaking changes, and upgrade notes.
Next generation testing framework powered by Vite StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
releases
7
breaking
3
security
0
deprecated
0
migrations
0
upgrade risk
Breaking changes and deprecations
Risky changes are separated from normal feature notes so you can scan upgrade impact before changing production dependencies.
migration notes
Source-backed next steps
Migration steps and recommended actions are only shown when the upstream release notes support them.
# latest_releases
source-backedv5.0.0-beta.5highbreakingfeatureprereleaseJun 15, 2026
v5.0.0-beta.5
This release introduces several breaking changes, including changes to config file lookup, package inline, and browser session handling. New features include enhanced browser UI and CLI options, while bug fixes address issues with logging, imports, and test execution.
affected
Users relying on config file lookup from ancestor directories or using the `@vitest/runner` package will be affected.
action
Review breaking changes and update configurations accordingly.
release_signals
-Don't lookup config file from ancestor directories
-Inline `@vitest/runner` package, do not publish it anymore
-Allow mutating happy-dom/jsdom window object
-Expose `concurrencyId`/`workerId` on TestModule's diagnostics, make id 1-based
-Require `sessionId` for orchestrator html request
+Display nested mark trace in browser UI
+Add `--repeats` CLI option
+`thresholds.autoUpdate` to receive previous threshold as argument
v5.0.0-beta.4highbreakingfeatureprereleaseJun 1, 2026
v5.0.0-beta.4
This release introduces several breaking changes, including stricter behavior for hoistable methods and `toHaveTextContent`, along with a rewritten benchmark API. New features include enhanced browser trace view steps and HTML reporter single file output.
affected
Developers using hoistable methods, `toHaveTextContent`, or the benchmark API are affected by breaking changes.
action
Review breaking changes and update code accordingly.
release_signals
-Throw an error if hoistable methods are outside the top-level scope
-`toHaveTextContent` is now strict; use `toMatchTextContent` as an alternative
-Rewritten benchmark public API
-Enabled `locators.exact` by default in browser mode
+Show trace view steps in the browser editor panel
+Support HTML reporter single file output
v5.0.0-beta.3highbreakingfeatureprereleaseMay 19, 2026
v5.0.0-beta.3
This release introduces significant breaking changes, including requiring Node.js 22 and Vite 6.4, and adds new features like TypeScript build mode and improved browser testing capabilities. Several bug fixes and performance improvements are also included.
affected
Users must upgrade to Node.js 22 and Vite 6.4 to use this version.
action
Upgrade Node.js to version 22 and Vite to version 6.4.
release_signals
-Require Node.js 22 and Vite 6.4
-Fail `expect.poll` when function didn't resolve in time
+Support TypeScript build mode
+Expose logs recorded during the test
+Show aria tree on locator element error
+Support custom `kind` in `page.mark`
+Live update trace view on watch UI