what stackpulse tracks
Vitest releases from GitHub
StackPulse watches Vitest release notes and keeps the original source link close to every summary.
#stacks/
loading releases…
releases
breaking
security
deprecated
migrations
Next generation testing framework powered by Vite StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
what stackpulse tracks
StackPulse watches Vitest release notes and keeps the original source link close to every summary.
upgrade risk
Risky changes are separated from normal feature notes so you can scan upgrade impact before changing production dependencies.
migration notes
Migration steps and recommended actions are only shown when the upstream release notes support them.
This patch release fixes several bugs including process binding issues, async leak detection improvements, matcher fixes, and JSDOM compatibility updates.
Users experiencing issues with process binding, async leaks, matchers, or JSDOM compatibility may be affected.
Update to v5.0.2 if experiencing any of the fixed bugs.
This release introduces UI improvements and fixes several bugs related to trace attempts, static collection, automocking, and import resolution. It also includes minor enhancements to error handling and metadata management.
Users relying on deprecated configurations or encountering issues with trace attempts, static collection, or automocking will be affected.
Review deprecation warnings and update configurations if necessary.
Vitest 5.0.0 introduces significant performance improvements and new features while addressing long-standing bugs. This major release includes numerous breaking changes, deprecations, and requires updates to Node.js 22 and Vite 6.4.
Users of Vitest will need to update their test configurations and code to accommodate breaking changes, especially those using deprecated features or specific test utilities.
Review the breaking changes and migration steps carefully, update dependencies, and adjust test configurations as needed.
This release introduces breaking changes, new features, and bug fixes, including static file parsing by default in `vitest list`, promoting `clearCache` out of experimental status, and adding a link to open Playwright traces in the UI.
Users relying on dynamic file parsing in `vitest list` will be affected by the breaking change.
Update your code to handle static file parsing in `vitest list` if necessary.
This release candidate introduces several new features, including the promotion of `parseSpecifications` out of experimental, improvements to the UI for trace navigation and persistence, and a switch to `@vitest/istanbuljs` packages for coverage. It also includes numerous bug fixes and performance optimizations.
Developers using Vitest for testing may benefit from new UI features, improved coverage handling, and various bug fixes.
Upgrade to v5.0.0-rc.3 to take advantage of new features and fixes, but be cautious as it is a release candidate.
This patch release fixes several bugs in Vitest v4, including restoring the global concurrency limit for test lifecycle, improving browser testing reliability, and restricting mock redirections to the filesystem allowlist.
Users experiencing issues with test concurrency, browser testing, or mock redirections in Vitest v4 are affected.
Update to v4.1.11 if you encounter issues with test concurrency, browser testing, or mock redirections.
This release introduces new features like custom GitHub Actions summary titles and CSP support for snapshots, along with various bug fixes for browser testing, UI, and worker handling.
Users of Vitest's GitHub Actions reporter and browser testing features may be affected by the changes.
Update to v5.0.0-rc.2 to benefit from bug fixes and new features.
Vitest v5.0.0-rc.1 introduces several breaking changes including config inheritance updates and async assertion handling, alongside new features like test duration reporting and improved module support.
Users relying on previous configuration behaviors, test filtering syntax, or async assertion handling will need to update their tests.
Review breaking changes and update test configurations and assertions accordingly.
This beta release introduces several performance optimizations and new features, including a pluggable benchmark provider API and improved browser testing capabilities. It also includes breaking changes to config resolution and numerous bug fixes.
Users relying on the previous config resolution behavior will need to update their configuration.
Review breaking changes and test the beta version before upgrading in production environments.
This release introduces several breaking changes, including updates to `@sinonjs/fake-timers`, removal of the `webdriverio` package, and default clearing of mocks before each test. A new feature, `vi.when()`, has been added, and various bug fixes have been implemented across different modules.
Users relying on the `webdriverio` package or specific mocking behaviors will be affected.
Review breaking changes and update your test configurations accordingly.
This release includes bug fixes for browser-related fs access checks and external module resolution issues in the VM.
Users experiencing issues with fs access in browser commands or external module resolution in the VM are affected.
Update to v4.1.10 to resolve these issues.
Fixes fs access in builtin browser commands by checking file system access during command execution.
Users relying on builtin browser commands that access the file system may be affected by this bug fix.
Update to v3.2.7 if experiencing issues with builtin browser commands accessing the file system.
Bug fixes including import fixes with optimizer and query imports, browser session readiness improvements, and worker crash prevention.
Users experiencing issues with import optimizations, browser testing readiness, or worker crashes will benefit from these fixes.
Update to v4.1.9 if experiencing related issues.
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.
Users relying on config file lookup from ancestor directories or using the `@vitest/runner` package will be affected.
Review breaking changes and update configurations accordingly.
This release primarily addresses a bug related to pinning the last supported vite-node version.
Users relying on vite-node compatibility may be affected.
Update to ensure compatibility with the pinned vite-node version.
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.
Developers using hoistable methods, `toHaveTextContent`, or the benchmark API are affected by breaking changes.
Review breaking changes and update code accordingly.
This release introduces new options for the `api` module and fixes a bug related to the browser client's `cdp` API.
Developers using the `api` module or browser client `cdp` API may be affected.
Update to v3.2.5 to benefit from the new features and bug fixes.
This release focuses on bug fixes related to browser testing, including disabling the client `cdp` API under specific conditions and resolving issues with Playwright route handling.
Users relying on Vitest for browser testing may be affected by the fixes.
Update to version 4.1.8 to benefit from the bug fixes.
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.
Users must upgrade to Node.js 22 and Vite 6.4 to use this version.
Upgrade Node.js to version 22 and Vite to version 6.4.