# Vitest v0.29.0 — Release & Upgrade Intelligence
- **Product:** Vitest (https://vitest.dev)
- **Version:** v0.29.0
- **Released:** Feb 25, 2023
- **Impact Score:** 7/10
- **Breaking Changes:** Source flagged
- **Canonical Analysis:** https://changelogs.us/vitest/updates/v0.29.0/
## Executive Summary (TL;DR)
Vitest v0.29.0. Source highlight: This release makes some significant changes to how tests are running. If you were using `--no-threads` before, you might consider enabling `--single-thread` instead (because your tests are now running in `child_process` instead of a worker thread) or try our new performance optimization feature (dis
## Breaking Changes & Deprecations
- One of the potential breaking bug fixes is that environments do not share the same global scope anymore if you run them with `--no-isolate`, `--no-threads` or `--single-thread` - you might need to update your setup files if you were relying on a global variable before.
- One of the breaking changes includes adding a link to snapshots inside snapshot files, meaning you will need to update all your snapshots.
- 🚨 Breaking Changes - Vitest as peer dependency for coverage packages - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2836 [(94247)](https://github.com/vitest-dev/vitest/commit/94247f1b)
## New Features
- Add a link to the comment at the top of the snapshot file - by @btea in https://github.com/vitest-dev/vitest/issues/2867 (615e1)
- Add test seed to banner - by @btkostner in https://github.com/vitest-dev/vitest/issues/2877 (bdb39)
- Use custom source-map-support implementation - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2905 (6ff6c)
- Add an option to enable Vite optimizer - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2912 (af8de)
- Add support for coverage reporter options - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2690 (f8176)
- Automatic threshold updating - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2886 (e1652)
## Bug Fixes
- Tests with `node` and `jsdom` (and other environments) now don't share the same global scope, if you run them with `--no-isolate` or `--no-threads` flag. Vitest doesn't provide a way to restore the previous behavior as it is considered a bug.
- Wait for console.log to print a message before terminating a worker - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2861 (fbc54)
- Cleanup last mocked cache when call vi.doMock - by @mysteryven in https://github.com/vitest-dev/vitest/issues/2872 (65d71)
- Reload changed configuration file on watch mode - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2889 (4d277)
- **coverage**: Custom providers to work inside worker threads - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2817 (81604)