Bump vitest from 4.0.13 to 4.0.14 by dependabot[bot] · Pull Request #309 · GuilhermeStracini/guilhermestracini.github.io

dependabot · 2025-12-01T12:43:38Z

Bumps vitest from 4.0.13 to 4.0.14.

Release notes

v4.0.14

   🚀 Experimental Features

browser: Expose utils.configurePrettyDOM - by @sheremet-va in vitest-dev/vitest#9103 (2cc34)

runner: Add full names to tasks - by @macarie in vitest-dev/vitest#9087 (821aa)

ui: Add tabbed failure view for toMatchScreenshot with comparison slider - by @macarie in vitest-dev/vitest#8813 (c37c2)

   🐞 Bug Fixes

Externalize before caching - by @sheremet-va in vitest-dev/vitest#9077 (e1b2e)

Collect the duration of external imports - by @sheremet-va in vitest-dev/vitest#9097 (3326c)

Rename collect to import, remove prepare - by @sheremet-va in vitest-dev/vitest#9091 (1256b)

browser:

Unsubscribe onCancel on rpc destroy - by @AriPerkkio in vitest-dev/vitest#9088 (f5b72)

Revert the viewport scaling in non-ui mode #9018 - by @sheremet-va in vitest-dev/vitest#9072 and vitest-dev/vitest#9018 (64502)

coverage:

Invalidate circular modules correctly on rerun with coverage - by @aicest in vitest-dev/vitest#9096 (6f22c)

expect:

Allow function as standard schema - by @hi-ogawa in vitest-dev/vitest#9099 (ed8a2)

jsdom:

Reuse abort signals if possible - by @sheremet-va in vitest-dev/vitest#9090 (2c468)

pool:

Init VITEST_POOL_ID + VITEST_WORKER_ID before environment setup - by @AriPerkkio in vitest-dev/vitest#9085 (37918)

web-worker:

postMessage to send ports to workers - by @whitphx and @AriPerkkio in vitest-dev/vitest#9078 (9d176)

   🏎 Performance

Replace debug with obug - by @sxzz and @AriPerkkio in vitest-dev/vitest#9057 (acc51)

    View changes on GitHub

Commits

9ca74cf chore: release v4.0.14
821aa20 feat(runner): Add full names to tasks (#9087)
1256b5c fix: rename collect to import, remove prepare (#9091)
3326cc9 fix: collect the duration of external imports (#9097)
379185b fix(pool): init VITEST_POOL_ID + VITEST_WORKER_ID before environment setu...
2c468ee fix(jsdom): reuse abort signals if possible (#9090)
e1b2e08 fix: externalize before caching (#9077)
acc5152 perf: replace debug with obug (#9057)
See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 4.0.13 to 4.0.14. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.0.14/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 4.0.14 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>

dependabot · 2025-12-01T12:43:39Z

Labels

The following labels could not be found: dependencies, npm. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

semanticdiff-com · 2025-12-01T12:43:42Z

Review changes with

Changed Files

File	Status
package-lock.json	24% smaller
package.json	0% smaller

pr-code-reviewer · 2025-12-01T12:43:44Z

👋 Hi there!

Everything looks good!

_{^{Automatically generated with the help of gpt-3.5-turbo.

Feedback? Please don't hesitate to drop me an email at webber@takken.io.}}

coderabbitai · 2025-12-01T12:43:45Z

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.}

socket-security · 2025-12-01T12:44:04Z

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	vitest@4.0.13 ⏵ 4.0.14			⁺¹

View full report

socket-security · 2025-12-01T12:44:05Z

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		Low adoption: npm `obug` Location: Package overview From: package-lock.json → `npm/vitest@4.0.14` → `npm/obug@2.1.1` ℹ 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 `support@socket.dev`. 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/obug@2.1.1`. 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		Embedded URLs or IPs: npm `@vitest/expect` URLs: Object.is, http://underscorejs.org, https://nodejs.org/docs/latest-v22.x/api/assert.html#comparison-details, https://github.com/facebook/immutable-js, https://github.com/chaijs/loupe/blob/9b8a6deabcd50adc056a64fb705896194710c5c6/src/index.ts#L29, https://github.com/microsoft/TypeScript/issues/61068 Location: Package overview From: package-lock.json → `npm/vitest@4.0.14` → `npm/@vitest/expect@4.0.14` ℹ 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 `support@socket.dev`. 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/expect@4.0.14`. 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		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/vitest@4.0.14` → `npm/@vitest/runner@4.0.14` ℹ 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 `support@socket.dev`. 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/runner@4.0.14`. 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		Environment variable access: npm `obug` Location: Package overview From: package-lock.json → `npm/vitest@4.0.14` → `npm/obug@2.1.1` ℹ 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 `support@socket.dev`. 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/obug@2.1.1`. 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		Environment variable access: npm `obug` reads DEBUG Env Vars: DEBUG Location: Package overview From: package-lock.json → `npm/vitest@4.0.14` → `npm/obug@2.1.1` ℹ 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 `support@socket.dev`. 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/obug@2.1.1`. 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		Embedded URLs or IPs: npm `vitest` URLs: https://github.com/sinonjs/sinon/issues/1852#issuecomment-419622780, https://github.com/nodejs/node/blob/7c3dce0/lib/internal/modules/package_json_reader.js, browser.name, https://vitest.dev/config/browser/provider, 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, 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, 127.0.0.0, https://nodejs.org/docs/latest-v20.x/api/esm.html#resolution-algorithm, https://github.com/nodejs/node/pull/49038, 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://github.com/vitejs/vite/pull/20449, 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://nodejs.org/api/modules.html#built-in-modules-with-mandatory-node-prefix, vitest.module.id, vitest.mock.id, 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, 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, vitest.runtime.run, vitest.worker.id Location: Package overview From: package-lock.json → `npm/vitest@4.0.14` ℹ 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 `support@socket.dev`. 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@4.0.14`. 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

github-actions · 2025-12-01T12:44:22Z

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs

Update Required: Your current package installation script is outdated and will no longer receive updates.
Please update to the new installation script which can be found here https://infisical.com/docs/cli/overview#installation debian section

A new release of infisical is available: 0.38.0 -> v0.154.2

To update, run: sudo apt-get update && sudo apt-get install infisical

12:44PM INF scanning for exposed secrets...
12:44PM INF 258 commits scanned.
12:44PM INF scan completed in 293ms
12:44PM INF no leaks found

guibranco

Automatically approved by gstraccini[bot]

guibranco · 2025-12-01T12:45:20Z

@dependabot recreate

guibranco · 2025-12-01T12:58:34Z

@dependabot recreate

dependabot · 2025-12-01T13:31:17Z

Looks like vitest is up-to-date now, so this is no longer needed.

dependabot Bot assigned guibranco Dec 1, 2025

github-actions Bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Dec 1, 2025

guibranco enabled auto-merge (squash) December 1, 2025 12:44

gstraccini Bot added the ☑️ auto-merge Automatic merging of pull requests (gstraccini-bot) label Dec 1, 2025

gstraccini Bot approved these changes Dec 1, 2025

View reviewed changes

guibranco approved these changes Dec 1, 2025

View reviewed changes

gstraccini Bot added the 🤖 bot Automated processes or integrations label Dec 1, 2025

dependabot Bot closed this Dec 1, 2025

auto-merge was automatically disabled December 1, 2025 13:31
Pull request was closed

dependabot Bot deleted the dependabot/npm_and_yarn/vitest-4.0.14 branch December 1, 2025 13:31

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Bump vitest from 4.0.13 to 4.0.14#309

Bump vitest from 4.0.13 to 4.0.14#309
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/vitest-4.0.14

dependabot Bot commented on behalf of github Dec 1, 2025 •

edited

Loading

Uh oh!

dependabot Bot commented on behalf of github Dec 1, 2025

Uh oh!

semanticdiff-com Bot commented Dec 1, 2025 •

edited

Loading

Uh oh!

pr-code-reviewer Bot commented Dec 1, 2025 •

edited

Loading

Uh oh!

coderabbitai Bot commented Dec 1, 2025

Review skipped

Uh oh!

socket-security Bot commented Dec 1, 2025

Uh oh!

socket-security Bot commented Dec 1, 2025

Uh oh!

github-actions Bot commented Dec 1, 2025

Uh oh!

guibranco left a comment

Uh oh!

guibranco commented Dec 1, 2025

Uh oh!

guibranco commented Dec 1, 2025

Uh oh!

dependabot Bot commented on behalf of github Dec 1, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

dependabot Bot commented on behalf of github Dec 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

v4.0.14

🚀 Experimental Features

🐞 Bug Fixes

🏎 Performance

View changes on GitHub

Uh oh!

dependabot Bot commented on behalf of github Dec 1, 2025

Labels

Uh oh!

semanticdiff-com Bot commented Dec 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pr-code-reviewer Bot commented Dec 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

👋 Hi there!

Uh oh!

coderabbitai Bot commented Dec 1, 2025

Review skipped

Uh oh!

socket-security Bot commented Dec 1, 2025

Uh oh!

socket-security Bot commented Dec 1, 2025

Uh oh!

github-actions Bot commented Dec 1, 2025

Uh oh!

guibranco left a comment

Choose a reason for hiding this comment

Uh oh!

guibranco commented Dec 1, 2025

Uh oh!

guibranco commented Dec 1, 2025

Uh oh!

dependabot Bot commented on behalf of github Dec 1, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

dependabot Bot commented on behalf of github Dec 1, 2025 •

edited

Loading

semanticdiff-com Bot commented Dec 1, 2025 •

edited

Loading

pr-code-reviewer Bot commented Dec 1, 2025 •

edited

Loading