Bump vitest from 3.2.4 to 4.0.9 #327
Conversation
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 3.2.4 to 4.0.9. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.0.9/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 4.0.9 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
requested review from
a team,
CarlosGamero,
drdaemos and
kibertoad
as code owners
|
Note
|
| Cohort / File(s) | Summary |
|---|---|
Dependency Update package.json |
Updated vitest dev dependency from ^3.2.4 to ^4.0.9 |
Estimated code review effort
🎯 1 (Trivial) | ⏱️ ~2 minutes
- Single version number change with no code modifications
- No logic, control flow, or API changes to validate
- Standard dependency bump requiring only verification that the version range is appropriate
Pre-merge checks and finishing touches
❌ Failed checks (1 warning)
| Check name | Status | Explanation | Resolution |
|---|---|---|---|
| Description check | The description is largely incomplete compared to the template. It lacks the required 'Changes' section and the checklist with labels (major/minor/patch/skip-release) and documentation/test update confirmations. | Add a 'Changes' section explaining the update, complete the checklist by selecting a release label and confirming documentation and test status updates. |
✅ Passed checks (2 passed)
| Check name | Status | Explanation |
|---|---|---|
| Title check | ✅ Passed | The title clearly and accurately describes the main change: bumping vitest from version 3.2.4 to 4.0.9, which matches the package.json modification. |
| 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.9
📜 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(1 hunks)
🔇 Additional comments (1)
package.json (1)
82-82: Vitest 4.x compatibility verified — no code changes required.The codebase uses only standard vitest APIs (describe, it, expect, beforeEach, afterEach, vi, describe.each) which remain fully compatible with vitest 4.x. Configuration uses
reporters: ['verbose'](not the removed 'basic' reporter), standard pool settings, and v8 coverage—all compatible. No deprecated test signatures, deprecated config options, or affected mocking patterns (vi.restoreAllMocks, getMockName) are present. The test suite should run successfully without modifications.
Comment @coderabbitai help to get the list of available commands and usage tips.
|
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting |
|
Superseded by #333. |
Bumps vitest from 3.2.4 to 4.0.9.
Release notes
Sourced from vitest's releases.
... (truncated)
Commits
62fab24chore: release v4.0.95e750f4fix(forks): increase worker start timeout (#9027)506a9fdfix(jsdom): cloned request is an instance ofRequest(#8985)46bfd09chore: release v4.0.8c79f47cfix(forks): do not fail with Windows Defender enabled (#8967)7ed99cdchore: remove unnecesseryvalues()call for set (#8964)9a9323bchore(deps): update dependency@antfu/eslint-configto v6 (#8832)46b3529chore(deps): update dependency jsdom to v27 (#8700)65292c3docs: update structure (#8625)da8b93afix(deps): update all non-major dependencies (#8636)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