chore(deps-dev): bump @vitest/coverage-v8 from 2.1.9 to 3.2.6#191
chore(deps-dev): bump @vitest/coverage-v8 from 2.1.9 to 3.2.6#191dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) from 2.1.9 to 3.2.6. - [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/v3.2.6/packages/coverage-v8) --- updated-dependencies: - dependency-name: "@vitest/coverage-v8" dependency-version: 3.2.6 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
dependabot
Bot
requested review from
ruili-testsprite and
zeshi-du
as code owners
WalkthroughUpdated the ChangesDependency update
Estimated code review effort: 1 (Trivial) | ~2 minutes Related Issues: Not specified. Related PRs: Not specified. Suggested labels: dependencies Suggested reviewers: Not specified. 🐰 A tiny hop, a version raised, 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@package.json`:
- Line 59: The Vitest packages are out of sync: package.json has
`@vitest/coverage-v8` at 3.2.6 while the lockfile still pins vitest and vite-node
to 2.1.9. Update the full Vitest stack together in the dependency declarations
and regenerate the lockfile so vitest, vite-node, and `@vitest/coverage-v8`
resolve to compatible versions.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: efde8154-53f6-4834-aa65-b1858d533a35
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json,!package-lock.json
📒 Files selected for processing (1)
package.json
| "@eslint/js": "^9.14.0", | ||
| "@types/node": "^22.9.0", | ||
| "@vitest/coverage-v8": "^2.1.4", | ||
| "@vitest/coverage-v8": "^3.2.6", |
There was a problem hiding this comment.
🩺 Stability & Availability | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
rg -n '"vitest"|"vite-node"|`@vitest/coverage-v8`' package.json package-lock.json pnpm-lock.yaml yarn.lockRepository: TestSprite/testsprite-cli
Length of output: 1000
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Show the root package dependencies and the installed vitest / vite-node entries.
sed -n '1,80p' package-lock.json
printf '\n--- vitest-related blocks ---\n'
rg -n -A8 -B4 '"node_modules/vitest"|\"node_modules/vite-node\"|\"node_modules/@vitest/coverage-v8\"' package-lock.jsonRepository: TestSprite/testsprite-cli
Length of output: 3051
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Show the exact lockfile blocks for Vitest packages.
for pkg in '`@vitest/coverage-v8`' vitest 'vite-node'; do
printf '\n===== %s =====\n' "$pkg"
rg -n -A14 -B4 --fixed-strings "\"node_modules/$pkg\"" package-lock.json
doneRepository: TestSprite/testsprite-cli
Length of output: 2525
🏁 Script executed:
#!/bin/bash
set -euo pipefail
sed -n '1612,1645p' package-lock.jsonRepository: TestSprite/testsprite-cli
Length of output: 1286
Align the Vitest versions before merging.
package-lock.json still resolves vitest and vite-node to 2.1.9, but @vitest/coverage-v8@3.2.6 requires vitest@3.2.6. Update the Vitest stack in lockstep and regenerate the lockfile.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@package.json` at line 59, The Vitest packages are out of sync: package.json
has `@vitest/coverage-v8` at 3.2.6 while the lockfile still pins vitest and
vite-node to 2.1.9. Update the full Vitest stack together in the dependency
declarations and regenerate the lockfile so vitest, vite-node, and
`@vitest/coverage-v8` resolve to compatible versions.
Bumps @vitest/coverage-v8 from 2.1.9 to 3.2.6.
Release notes
Sourced from @vitest/coverage-v8's releases.
... (truncated)
Commits
b6d56f8chore: release v3.2.616f120dfix: pin last supported vite-node version2cbad0achore: release v3.2.5385a1aefix(browser): disable clientcdpAPI whenallowWrite/allowExec: false[ba...c666d14chore: release v3.2.4b87ee3echore: release v3.2.37ddcd33chore: release v3.2.2f858f3bchore: release v3.2.159200aechore: release v3.2.0407c0e4fix(coverage): in-source test cases excluded (#7985)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for
@vitest/coverage-v8since your current version.Most Recent Ignore Conditions Applied to This Pull Request
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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Summary by CodeRabbit