fix: batchRequests type constraint #462
Merged
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. ⚠ Warning: custom changes will be lost. |
jasonkuhrt
changed the title
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.
This PR contains the following updates:
^0.28.2->^0.29.0Release Notes
vitest-dev/vitest
v0.29.1Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.29.0Compare Source
This release makes some significant changes to how tests are running. If you were using
--no-threadsbefore, you might consider enabling--single-threadinstead (because your tests are now running inchild_processinstead of a worker thread) or try our new performance optimization feature (discussed later). If you were relying on API that was not available inside a worker (likeprocess.chdir(), you can now use this option.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-threadsor--single-thread- you might need to update your setup files if you were relying on a global variable before.If you had performance issues on large code bases before, try the new
deps.experimentalOptimizeroption instead of disabling threads. Feedback is welcome!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
NODE_V8_COVERAGE- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2786 (095c6)nodeandjsdom(and other environments) now don't share the same global scope, if you run them with--no-isolateor--no-threadsflag. Vitest doesn't provide a way to restore the previous behavior as it is considered a bug.chid_processmight run longer due to the communication overhead. If you want to restore the previous behavior, use--single-thread.🚀 Features
🐞 Bug Fixes
View changes on GitHub
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.