[Snyk] Upgrade @vitest/ui from 2.1.5 to 2.1.8 #114
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.
Snyk has created this PR to upgrade @vitest/ui from 2.1.5 to 2.1.8.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 3 versions ahead of your current version.
The recommended version was released 23 days ago.
Release notes
Package name: @vitest/ui
🐞 Bug Fixes
View changes on GitHub
🐞 Bug Fixes
pnpm.overrides
or yarn resolutions to override thevite
version in thevitest
package - the APIs are compatible.View changes on GitHub
🚀 Features
View changes on GitHub
🐞 Bug Fixes
dangerouslyIgnoreUnhandledErrors
without base reporter - by @ AriPerkkio in #6808 (0bf0a)unhandledRejection
even when base reporter is not used - by @ AriPerkkio in #6812 (8878b)sequence.concurrent
from theRuntimeConfig
type - by @ sheremet-va in #6880 (6af73).poll
,.element
,.rejects
/.resolves
, andlocator.*
weren't awaited - by @ sheremet-va in #6877 (93b67)enter
or'a'
- by @ AriPerkkio in #6848 (487c8)🏎 Performance
View changes on GitHub
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: