Conversation
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 3.2.4 to 4.0.17. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.0.17/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 4.0.17 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
|
Note
|
| Cohort / File(s) | Summary |
|---|---|
Dependency version upgrade package.json |
Upgraded vitest from ^3.2.4 to ^4.0.17 |
Estimated code review effort
🎯 1 (Trivial) | ⏱️ ~2 minutes
🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 warning)
| Check name | Status | Explanation | Resolution |
|---|---|---|---|
| Description check | The description is missing required checklist items: no label selection (major/minor/patch/skip-release) is marked, and documentation/test update status is not indicated per the template. | Add completed checklist items: select an appropriate label and confirm documentation and test update status as required by the template. |
✅ Passed checks (2 passed)
| Check name | Status | Explanation |
|---|---|---|
| Title check | ✅ Passed | The title accurately and concisely describes the main change: bumping vitest from version 3.2.4 to 4.0.17, which directly matches the changeset. |
| Docstring Coverage | ✅ Passed | No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. |
✏️ Tip: You can configure your own custom pre-merge checks in the settings.
📜 Recent 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
🔇 Additional comments (1)
package.json (1)
58-58: Verify tests pass after upgrading Vitest.While upgrading to Vitest 4.0, ensure all tests continue to pass. The codebase uses basic
vi.spyOn()patterns which should continue to work without issues in this version.Likely an incorrect or invalid review comment.
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: 0
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: Version mismatch:@vitest/coverage-v8must be upgraded to match vitest 4.x.The latest version of
@vitest/coverage-v8is 4.0.16, and vitest ecosystem packages are expected to be kept in sync. The current@vitest/coverage-v8: ^3.2.4at line 52 is incompatible withvitest: ^4.0.17at line 58 and will likely causenpm run test:coverageto fail.Vitest 4's V8 code coverage provider uses more accurate coverage result remapping logic, and it is expected for users to see changes in their coverage reports when updating from Vitest v3.
🔧 Proposed fix
- "@vitest/coverage-v8": "^3.2.4", + "@vitest/coverage-v8": "^4.0.17",Also applies to: 58-58
📜 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
🔇 Additional comments (1)
package.json (1)
58-58: Verify tests pass after upgrading Vitest.While upgrading to Vitest 4.0, ensure all tests continue to pass. The codebase uses basic
vi.spyOn()patterns which should continue to work without issues in this version.Likely an incorrect or invalid review comment.
|
Superseded by #253. |
Bumps vitest from 3.2.4 to 4.0.17.
Release notes
Sourced from vitest's releases.
... (truncated)
Commits
dd54e94chore: release v4.0.1759f92d4fix(fsModuleCache): add importers alongside importedModules (#9423)751364efix(fsModuleCache): don't store importers in cache (#9422)4b67fc2fix: typo in browser.provider error (#9394)40841fffix: handle null options inaddEventHandler#9371 (#9372)200dadbfix(pool): handle worker start failures gracefully (#9337)1500654fix(browser): supportfileParallelismon an instance (#9328)a8a8836fix(pool): validate environment options when reusing the worker (#9349)7b10ab4fix(typecheck): improve error message when tsc outputs help text (#9214)876cb84feat: support TRACEPARENT and TRACESTATE environment variables for OpenTeleme...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.