Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Downgrade vitest to 2.0.0 #3148

Merged
merged 2 commits into from
Mar 19, 2025
Merged

Downgrade vitest to 2.0.0 #3148

merged 2 commits into from
Mar 19, 2025

Conversation

huchenlei
Copy link
Member

@huchenlei huchenlei commented Mar 19, 2025

Ref: vitest-dev/vscode#548 (comment)

Downgrade vitest to make debug test possible with vscode extension.

┆Issue is synchronized with this Notion page by Unito

@huchenlei huchenlei requested a review from a team as a code owner March 19, 2025 18:16
@huchenlei huchenlei added the dependencies Pull requests that update a dependency file label Mar 19, 2025
Copy link

socket-security bot commented Mar 19, 2025

New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/[email protected]2.0.0 Transitive: filesystem, network, shell, unsafe +106 14.1 MB vitestbot

View full report↗︎

Copy link

socket-security bot commented Mar 19, 2025

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package NoteSourceCI
Critical CVE npm/[email protected] ⚠︎

View full report↗︎

Next steps

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

@huchenlei huchenlei requested a review from a team as a code owner March 19, 2025 18:19
@huchenlei huchenlei merged commit 5bbceea into main Mar 19, 2025
10 checks passed
@huchenlei huchenlei deleted the downgrade_vitest branch March 19, 2025 18:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant