Repository navigation
Update Vitest to 5.0.3 to stop leaking temp directories - #1648
Merged
Merged
Conversation
Vitest 5.0.0 leaves a directory under /tmp after every run, so machines that run the suite often fill up their /tmp (vitest-dev/vitest#11224). 5.0.3 fixed this (vitest-dev/vitest#11248). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Vitest 5.0.0 leaves a directory under /tmp after every run, so machines that run the suite often fill up their /tmp (vitest-dev/vitest#11224). 5.0.3 fixed this (vitest-dev/vitest#11248).
Production notes
5.0.4 is out but younger than the
min-release-age=3gate in.npmrc, so 5.0.3 is the newest allowed patch. Running the suite withTMPDIRset to an empty directory left a<nanoid>/client/directory of 480 files behind on 5.0.0 and nothing on 5.0.3. Outside UTC,DateTimeDisplay.spec.ts"renders the instant formatted in the host timezone" can fail on both versions: under Europe/Berlin with an en-US locale it looks for "14" in 12-hour output.