Skip to content

Update vitest 4.0.13 → 4.0.14 (patch) #457

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.

Sign up for GitHub

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

Jump to bottom
Closed
depfu wants to merge 1 commit into from
Closed

Update vitest 4.0.13 → 4.0.14 (patch) #457

depfu wants to merge 1 commit into from

Conversation

@depfu
Copy link
Contributor

@depfu depfu bot commented Nov 26, 2025 •
edited
Loading

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ vitest (4.0.13 → 4.0.14) · Repo

Release Notes

4.0.14

   🚀 Experimental Features

   🐞 Bug Fixes

   🏎 Performance

    View changes on GitHub

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 20 commits:

↗️ @​vitest/expect (indirect, 4.0.13 → 4.0.14) · Repo

Release Notes

4.0.14

   🚀 Experimental Features

   🐞 Bug Fixes

   🏎 Performance

    View changes on GitHub

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 20 commits:

↗️ @​vitest/mocker (indirect, 4.0.13 → 4.0.14) · Repo

Release Notes

4.0.14

   🚀 Experimental Features

   🐞 Bug Fixes

   🏎 Performance

    View changes on GitHub

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 20 commits:

↗️ @​vitest/runner (indirect, 4.0.13 → 4.0.14) · Repo

Release Notes

4.0.14

   🚀 Experimental Features

   🐞 Bug Fixes

   🏎 Performance

    View changes on GitHub

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 20 commits:

↗️ @​vitest/snapshot (indirect, 4.0.13 → 4.0.14) · Repo

Release Notes

4.0.14

   🚀 Experimental Features

   🐞 Bug Fixes

   🏎 Performance

    View changes on GitHub

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 20 commits:

↗️ @​vitest/spy (indirect, 4.0.13 → 4.0.14) · Repo

Release Notes

4.0.14

   🚀 Experimental Features

   🐞 Bug Fixes

   🏎 Performance

    View changes on GitHub

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 20 commits:

🆕 obug (added, 2.1.1)

🆕 @​vitest/pretty-format (added, 4.0.14)

🆕 @​vitest/utils (added, 4.0.14)

Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
Go to the Depfu Dashboard to see the state of your dependencies and to customize how Depfu works.

@depfu depfu bot added the depfu label Nov 26, 2025
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Nov 26, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions github-actions bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Nov 26, 2025
@deepsource-io
Copy link

deepsource-io bot commented Nov 26, 2025 •
edited
Loading

Here's the code health analysis summary for commits 4a7f6a1..cb66163. View details on DeepSource ↗.

Analysis Summary

AnalyzerStatusSummaryLink
DeepSource JavaScript LogoJavaScript✅ SuccessView Check ↗
DeepSource Secrets LogoSecrets✅ SuccessView Check ↗
💡 If you’re a repository administrator, you can configure the quality gates from the settings.

@socket-security
Copy link

socket-security bot commented Nov 26, 2025 •
edited
Loading

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Updatedvitest@​4.0.13 ⏵ 4.0.149810079 +199 +1100

View full report

@socket-security
Copy link

socket-security bot commented Nov 26, 2025 •
edited
Loading

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Block Medium
Low adoption: npm obug

Location: Package overview

From: package-lock.json → npm/[email protected] → npm/[email protected]

ℹ Read more on: This package | This alert | What are unpopular packages?

Next steps: 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 [email protected].

Suggestion: Unpopular packages may have less maintenance and contain other problems.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Low
Embedded URLs or IPs: npm @vitest/runner

URLs: https://developer.mozilla.org/en-US/docs/Web/API/AbortSignal, https://vitest.dev/guide/test-context#signal, https://vitest.dev/guide/test-context#ontestfailed, https://vitest.dev/guide/test-context#ontestfinished, https://vitest.dev/guide/test-context#skip, https://vitest.dev/guide/test-context#annotate, https://vitest.dev/advanced/runner#your-task-function, https://github.com/unocss/unocss/blob/2e74b31625bbe3b9c8351570749aa2d3f799d919/packages/autocomplete/src/parse.ts#L11, https://github.com/vitest-dev/vitest/pull/7069, vitest.test.id, vitest.test.name, vitest.suite.id, vitest.suite.name

Location: Package overview

From: package-lock.json → npm/[email protected] → npm/@vitest/[email protected]

ℹ Read more on: This package | This alert | What are URL strings?

Next steps: 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 [email protected].

Suggestion: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@vitest/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Low
Environment variable access: npm obug

Location: Package overview

From: package-lock.json → npm/[email protected] → npm/[email protected]

ℹ Read more on: This package | This alert | What is environment variable access?

Next steps: 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 [email protected].

Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Low
Environment variable access: npm obug reads DEBUG

Env Vars: DEBUG

Location: Package overview

From: package-lock.json → npm/[email protected] → npm/[email protected]

ℹ Read more on: This package | This alert | What is environment variable access?

Next steps: 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 [email protected].

Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Low
Embedded URLs or IPs: npm vitest

URLs: https://github.com/nodejs/node/blob/7c3dce0/lib/internal/modules/package_json_reader.js, browser.name, https://vitest.dev/config/browser/provider, https://github.com/sinonjs/sinon/issues/1852#issuecomment-419622780, https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#setting-an-error-message, https://github.com/actions/toolkit/blob/f1d9b4b985e6f0f728b4b766db73498403fd5ca3/packages/core/src/command.ts#L80-L85, https://github.com/vitest-dev/vitest/issues, https://gist.github.com/john-doherty/b9195065884cdbfd2017a4756e6409cc, task.name, https://vitest.dev/guide/coverage.html#including-and-excluding-files-from-coverage-report, https://istanbul.js.org/docs/advanced/alternative-reporters/, https://trace.playwright.dev/, https://vitest.dev/api/browser/commands, https://vitest.dev/config/#onunhandlederror, https://vitest.dev/config/#root, https://vitest.dev/api/#test, https://nodejs.org/docs/latest/api/cli.html, https://github.com/nodejs/node/issues/41103, https://github.com/chaijs/chai/blob/4.x.x/lib/chai/config.js, https://vitest.dev/guide/open-telemetry, builder.io/qwik, https://playwright.dev, https://webdriver.io, builder.io/qwik/optimizer, qwik.dev/core, https://vitest.dev/config/browser/playwright, https://vitest.dev/config/browser/webdriverio, https://github.com/vitejs/vite/pull/20449, https://www.cl.cam.ac.uk/%7Emgk25/ucs/utf8_check.c, https://tools.ietf.org/html/rfc6455#section-9.1, https://html.spec.whatwg.org/multipage/comms.html#the-websocket-interface, https://github.com/websockets/ws/issues/1869., https://github.com/websockets/ws/issues/1940., https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_Expressions#escaping, https://github.com/vitest-dev/vitest/pull/7531, vitest.fetched_module.id, https://github.com/vitejs/vite/issues/15438,, https://nodejs.org/api/process.html#signal-events, https://github.com/vitest-dev/vitest/issues/7871, vitest.worker.name, https://github.com/jestjs/jest/blob/25a8785584c9d54a05887001ee7f498d489a5441/packages/jest-worker/src/workers/ChildProcessWorker.ts#L463-L477, https://github.com/tinylibs/tinypool/blob/40b4b3eb926dabfbfd3d0a7e3d1222d4dd1c0d2d/src/runtime/process-worker.ts#L56, https://github.com/vitejs/vite/blob/af2aa09575229462635b7cbb6d248ca853057ba2/packages/vite/src/node/plugins/resolve.ts#L1056-L1080, https://github.com/vitejs/vite/blob/main/packages/vite/src/node/logger.ts?rgh-link-date=2024-10-16T23%3A29%3A19Z, https://github.com/vitejs/vite/pull/15184, https://github.com/vitejs/vite/pull/20502, https://github.com/unjs/mlly/blob/c5bcca0cda175921344fd6de1bc0c499e73e5dac/src/syntax.ts#L51-L98, https://github.com/vitejs/vite/issues/14328, https://vitest.dev/guide/projects, https://vitest.dev/config/#reporters, https://vitest.dev/api/vi#vi-advancetimersbytime, https://vitest.dev/api/vi#vi-fn, https://vitest.dev/api/mock, performance.now, Date.now, https://vitest.dev/api/vi#vi-waitfor, https://vitest.dev/api/vi#vi-mock, 0.0.0.0, process.env.CI, https://vitest.dev/config/#coverage-reporter, https://github.com/istanbuljs/nyc#coverage-thresholds, https://github.com/istanbuljs/nyc#ignoring-methods, https://vitest.dev/guide/coverage#custom-coverage-provider, https://en.wikipedia.org/wiki/Random_seed, https://vitest.dev/config/#sequence-hooks, 127.0.0.1:9229, vitest.runtime.run, vitest.worker.id, https://nodejs.org/api/modules.html#built-in-modules-with-mandatory-node-prefix, vitest.module.id, vitest.mock.id, 127.0.0.0, https://nodejs.org/docs/latest-v20.x/api/esm.html#resolution-algorithm, https://github.com/nodejs/node/pull/49038

Location: Package overview

From: package-lock.json → npm/[email protected]

ℹ Read more on: This package | This alert | What are URL strings?

Next steps: 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 [email protected].

Suggestion: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@guibranco guibranco enabled auto-merge (squash) November 26, 2025 15:11
@gstraccini gstraccini bot added the ☑️ auto-merge Automatic merging of pull requests (gstraccini-bot) label Nov 26, 2025
guibranco
guibranco approved these changes Nov 26, 2025
View reviewed changes
Copy link
Owner

@guibranco guibranco left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automatically approved by gstraccini[bot]

guibranco
guibranco approved these changes Nov 26, 2025
View reviewed changes
Copy link
Owner

@guibranco guibranco left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automatically approved by gstraccini[bot]

@gstraccini gstraccini bot added the 🤖 bot Automated processes or integrations label Nov 26, 2025
@guibranco
Copy link
Owner

guibranco commented Nov 26, 2025

@depfu merge

1 similar comment
@guibranco
Copy link
Owner

guibranco commented Nov 26, 2025

@depfu merge

@depfu depfu bot force-pushed the depfu/update/npm/vitest-4.0.14 branch from b7ae7a6 to cb66163 Compare November 26, 2025 15:11
@sonarqubecloud
Copy link

sonarqubecloud bot commented Nov 26, 2025

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

@github-actions
Copy link

github-actions bot commented Nov 26, 2025

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs 
2025-11-26T15:12:05Z INF scanning for exposed secrets...
3:12PM INF 429 commits scanned.
2025-11-26T15:12:05Z INF scan completed in 671ms
2025-11-26T15:12:05Z INF no leaks found

@depfu
Copy link
Contributor Author

depfu bot commented Nov 26, 2025

Closing because this update has already been applied

@depfu depfu bot closed this Nov 26, 2025
auto-merge was automatically disabled November 26, 2025 15:17

Pull request was closed

@depfu depfu bot deleted the depfu/update/npm/vitest-4.0.14 branch November 26, 2025 15:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@guibranco guibranco guibranco approved these changes

@gstraccini gstraccini[bot] gstraccini[bot] approved these changes

Assignees

@guibranco guibranco

Labels

☑️ auto-merge Automatic merging of pull requests (gstraccini-bot) 🤖 bot Automated processes or integrations depfu size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@guibranco