Bump vitest from 3.2.4 to 4.0.14 #236
Conversation
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 3.2.4 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-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
requested review from
a team,
CarlosGamero and
drdaemos
as code owners
|
Note
|
| Cohort / File(s) | Summary |
|---|---|
Dependency Update package.json |
Updated devDependency vitest from ^3.2.4 to ^4.0.14 |
Estimated code review effort
🎯 1 (Trivial) | ⏱️ ~2 minutes
Pre-merge checks and finishing touches
❌ Failed checks (1 warning)
| Check name | Status | Explanation | Resolution |
|---|---|---|---|
| Description check | The PR description is comprehensive with release notes, but lacks the required template sections: 'Changes' description and checklist with labels/documentation/test updates. | Add a 'Changes' section describing the update, and complete the checklist confirming label application and whether documentation/tests were updated. |
✅ Passed checks (2 passed)
| Check name | Status | Explanation |
|---|---|---|
| Title check | ✅ Passed | The PR title clearly and concisely summarizes the main change: bumping vitest from version 3.2.4 to 4.0.14, which is the sole purpose of the changeset. |
| Docstring Coverage | ✅ Passed | No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. |
✨ Finishing touches
🧪 Generate unit tests (beta)
- Create PR with unit tests
- Post copyable unit tests in a comment
- Commit unit tests in branch
dependabot/npm_and_yarn/vitest-4.0.14
Comment @coderabbitai help to get the list of available commands and usage tips.
![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
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
package.json (1)
52-52: Update@vitest/coverage-v8to match vitest version.The latest version of @vitest/coverage-v8 is 4.0.14, which is required to be compatible with vitest 4.0.14. Keeping it at ^3.2.4 will break the
test:coveragescript (line 30).- "@vitest/coverage-v8": "^3.2.4", + "@vitest/coverage-v8": "^4.0.14",
📜 Review details
Configuration used: Repository: lokalise/coderabbit/.coderabbit.yaml
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
- Jira integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (1)
package.json(1 hunks)
| "tsup": "^8.5.0", | ||
| "typescript": "^5.9.2", | ||
| "vitest": "^3.2.4", | ||
| "vitest": "^4.0.14", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify vitest and coverage plugin compatibility, and check for custom vitest config
# 1. Check if vitest.config.ts/js exists and may need migration updates
echo "=== Checking for vitest config files ==="
fd -e ts -e js 'vitest\.config' 2>/dev/null || echo "No vitest.config found"
# 2. Verify node_modules would resolve correct versions (check package-lock or similar)
if [ -f "package-lock.json" ]; then
echo "=== vitest version constraint in package-lock.json ==="
grep -A 2 '"vitest":' package-lock.json | head -10
echo "=== @vitest/coverage-v8 version constraint in package-lock.json ==="
grep -A 2 '"@vitest/coverage-v8":' package-lock.json | head -10
fi
# 3. Check for custom reporters or test hooks that may use removed APIs
echo "=== Searching for potential removed Vitest API usage ==="
rg -n '(onCollected|onSpecsCollected|onPathsCollected|onTaskUpdate|onFinished)' --type ts --type js 2>/dev/null || echo "No matches found"
# 4. List test-related files to understand the scope
echo "=== Test files in the repo ==="
fd -e test.ts -e test.js -e spec.ts -e spec.js 2>/dev/null | head -20Repository: lokalise/node-core
Length of output: 844
🏁 Script executed:
#!/bin/bash
# Check for mock usage and snapshot files
# 1. Search for vi.fn() usage (mocks that might be affected by getMockName() change)
echo "=== Searching for vi.fn() mock usage ==="
rg -n 'vi\.fn\(\)' --type ts --type js 2>/dev/null || echo "No vi.fn() usage found"
# 2. Search for getMockName() usage
echo "=== Searching for getMockName() usage ==="
rg -n 'getMockName' --type ts --type js 2>/dev/null || echo "No getMockName() usage found"
# 3. Check for snapshot files
echo "=== Snapshot files ==="
fd -e snap -e snap.ts 2>/dev/null || echo "No snapshot files found"
# 4. Check package.json for coverage or reporter configuration
echo "=== Checking package.json for vitest configuration ==="
cat package.json | grep -A 30 '"vitest"' || echo "No explicit vitest config in package.json"
# 5. Check for any coverage plugin references
echo "=== Checking for coverage plugin references ==="
rg -n '@vitest/coverage|coverage' package.json 2>/dev/null || echo "No coverage plugin found"Repository: lokalise/node-core
Length of output: 1597
🏁 Script executed:
#!/bin/bash
# Check coverage plugin version alignment
echo "=== Current versions ==="
echo "vitest: ^4.0.14"
echo "@vitest/coverage-v8: ^3.2.4"
# Search for any configuration files or docs about versions
echo ""
echo "=== Checking for version-related docs or config ==="
fd -e md 2>/dev/null | xargs grep -l "vitest\|coverage" 2>/dev/null | head -5
echo ""
echo "=== Checking test scripts that might fail ==="
rg -n 'describe|test|it\(' src/utils/objectUtils.spec.ts -A 2 | head -30Repository: lokalise/node-core
Length of output: 1164
Update @vitest/coverage-v8 to v4 for compatibility with vitest 4.0.
The coverage plugin is pinned to v3.2.4 while vitest is at v4.0.14. Update @vitest/coverage-v8 to ^4.0.0 or later to ensure compatibility. The codebase does not use removed APIs (onCollected, onSpecsCollected, etc.) or custom reporters, so standard vitest 4 migration should not cause issues beyond this dependency version mismatch.
🤖 Prompt for AI Agents
In package.json around line 58, the @vitest/coverage-v8 dependency is pinned to
v3 while vitest is v4.0.14 causing a compatibility mismatch; update the
package.json entry for "@vitest/coverage-v8" to "^4.0.0" (or later compatible
v4.x) and run npm/yarn install to update lockfile, then run the test/coverage
script to verify no breaking changes.
|
Superseded by #241. |
Bumps vitest from 3.2.4 to 4.0.14.
Release notes
Sourced from vitest's releases.
... (truncated)
Commits
9ca74cfchore: release v4.0.14821aa20feat(runner): Add full names to tasks (#9087)1256b5cfix: renamecollecttoimport, removeprepare(#9091)3326cc9fix: collect the duration of external imports (#9097)379185bfix(pool): initVITEST_POOL_ID+VITEST_WORKER_IDbefore environment setu...2c468eefix(jsdom): reuse abort signals if possible (#9090)e1b2e08fix: externalize before caching (#9077)acc5152perf: replacedebugwithobug(#9057)73b54cechore: release v4.0.13b27e002perf: avoid fetchModule roundtrip if the module is cached (#9075)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for vitest since your current version.
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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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
✏️ Tip: You can customize this high-level summary in your review settings.