| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 4.0.8 to 4.1.0. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.0/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 4.1.0 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 49e87c0. Configure here.
Sorry, something went wrong.
| '@vitest/coverage-v8': | ||
| specifier: 4.0.8 | ||
| version: 4.0.8(vitest@4.0.8(@types/debug@4.1.12)(@types/node@24.5.0)(jiti@2.5.1)(lightningcss@1.32.0)(terser@5.46.0)(yaml@2.8.3)) | ||
| version: 4.0.8(vitest@4.1.0(@types/node@25.9.1)(vite@7.3.2(@types/node@25.9.1)(jiti@2.5.1)(lightningcss@1.32.0)(terser@5.48.0)(yaml@2.8.3))) |
There was a problem hiding this comment.
High Severity
@vitest/coverage-v8 is pinned at 4.0.8 in package.json and declares an exact peer dependency on vitest: 4.0.8, but vitest was bumped to 4.1.0. This peer dependency mismatch means the coverage tool may be incompatible with the new vitest version, potentially causing test coverage collection to fail or produce incorrect results. The @vitest/coverage-v8 package needs to be bumped to 4.1.0 alongside vitest.
Additional Locations (1)Reviewed by Cursor Bugbot for commit 49e87c0. Configure here.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Bumps vitest from 4.0.8 to 4.1.0.
Release notesSourced from vitest's releases.
... (truncated)
CommitsDependabot 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:
You can disable automated security fix PRs for this repo from the Security Alerts page.