Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 1, 2025

Bumps vitest from 4.0.9 to 4.0.14.

Release notes

Sourced from vitest's releases.

v4.0.14

   🚀 Experimental Features

   🐞 Bug Fixes

   🏎 Performance

    View changes on GitHub

v4.0.13

   🐞 Bug Fixes

   🏎 Performance

    View changes on GitHub

v4.0.12

   🐞 Bug Fixes

... (truncated)

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)
  • 73b54ce chore: release v4.0.13
  • b27e002 perf: avoid fetchModule roundtrip if the module is cached (#9075)
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

Summary by cubic

Updated Vitest to 4.0.15 to bring bug fixes and performance improvements for our test suite. No app code changes required.

  • Dependencies
    • Bumped vitest from 4.0.9 to 4.0.15.
    • Upstream improvements: faster logging (debug → obug), runner shows full task names, coverage rerun fix, jsdom abort signal reuse, and improved screenshot failure UI.
    • Note: transitive tinyexec now requires Node 18+.

Written for commit 7d93047. Summary will update automatically on new commits.

@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Dec 1, 2025
@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Dec 1, 2025

Deploying blinklabs-vpn with  Cloudflare Pages  Cloudflare Pages

Latest commit: 7d93047
Status:🚫  Build failed.

View logs

@dependabot dependabot bot added the javascript Pull requests that update javascript code label Dec 1, 2025
@coderabbitai
Copy link

coderabbitai bot commented Dec 1, 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.

Copy link

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

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

No issues found across 2 files

@fossabot
Copy link

fossabot bot commented Dec 1, 2025

fossabot is Thinking

@fossabot
Copy link

fossabot bot commented Dec 1, 2025

Needs Review

I recommend reviewing this upgrade before merging because Vitest now requires Node.js 20+ while the project lacks explicit version enforcement in package.json. The codebase does not use any of the deprecated APIs that were removed in the major version upgrade (poolMatchGlobs, environmentMatchGlobs, or third test parameter), and all test imports use relative paths avoiding the absolute import breaking change. The project uses native fetch rather than Axios, avoiding known MSW compatibility issues. However, without enforced Node.js version requirements, CI/CD pipelines or developer environments running Node.js 18 will fail. Consider adding an engines field to package.json specifying Node.js 20+ to prevent runtime compatibility issues.

What we checked

  • vitest upgraded from 4.0.9 to 4.0.14, which requires Node.js 20+, but package.json lacks engines field to enforce this requirement [1]
  • Vitest configuration uses only standard options (globals, environment, setupFiles, coverage) - no deprecated APIs like poolMatchGlobs or environmentMatchGlobs detected [2]
  • Test imports use relative paths (../../test/utils), avoiding the absolute import breaking change that affects src/tests directories [3]
  • Tests use native fetch API via global.fetch mock, avoiding known Axios+MSW compatibility issues in Vitest 4 [4]
  • Vitest 4.0 breaking changes documentation confirms removal of deprecated config options and Node.js 20+ requirement, but codebase doesn't use any deprecated features [5]

Dependency Usage

Vitest serves as the complete testing infrastructure for this Cardano VPN frontend application, providing automated test coverage across critical business functions including API client operations, wallet connectivity features, and data-fetching hooks. The framework is integrated into the build toolchain through Vite configuration and package scripts, with additional developer productivity tools like UI-based test runners and code coverage reporting, ensuring quality assurance for the blockchain wallet integration and API communication layers that power the VPN service.

View 1 more usage
Less Important Usages (6)

These usages were analyzed but no breaking changes were detected:

vitest

Changes

Vitest has been upgraded with three breaking changes: replacing the 'debug' package with 'obug' (affecting Debugger imports), changing peer dependency from '@​types/debug' to '@​opentelemetry/api', and replacing VitestModuleRunner type with PublicModuleRunner interface. Key new capabilities include OpenTelemetry tracing support throughout test execution, experimental file system caching for improved performance between reruns, and an extensible test artifact API with a tabbed UI failure view for screenshot comparisons.

  • Replaced 'debug' package with 'obug' for internal debugging - this changes the Debugger import type from 'debug' to 'obug' (v4.0.14, package source)
  • Changed peer dependency from '@​types/debug' to '@​opentelemetry/api' (^1.9.0) for OpenTelemetry instrumentation support (v4.0.14, package source)
  • Replaced VitestModuleRunner type with PublicModuleRunner interface in loadDiffConfig() and loadSnapshotSerializers() function signatures (v4.0.14, package source)
View 115 more changes

View 18 more changes in the full analysis

References (5)

[1]: vitest upgraded from 4.0.9 to 4.0.14, which requires Node.js 20+, but package.json lacks engines field to enforce this requirement

"vitest": "^4.0.14"

[2]: Vitest configuration uses only standard options (globals, environment, setupFiles, coverage) - no deprecated APIs like poolMatchGlobs or environmentMatchGlobs detected

[3]: Test imports use relative paths (../../test/utils), avoiding the absolute import breaking change that affects src/tests directories

[4]: Tests use native fetch API via global.fetch mock, avoiding known Axios+MSW compatibility issues in Vitest 4

global.fetch = vi.fn().mockResolvedValueOnce({

[5]: Vitest 4.0 breaking changes documentation confirms removal of deprecated config options and Node.js 20+ requirement, but codebase doesn't use any deprecated features (source link)


fossabot analyzed this PR using static analysis and dependency research. View this analysis on the web

@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/vitest-4.0.14 branch 2 times, most recently from cf58bef to d7a946a Compare December 4, 2025 20:19
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 4.0.9 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] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/vitest-4.0.14 branch from d7a946a to 7d93047 Compare December 4, 2025 21:06
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 javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant