Bump vitest and @vitest/ui in /src/App - #1153
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) and [@vitest/ui](https://github.com/vitest-dev/vitest/tree/HEAD/packages/ui). These dependencies needed to be updated together. Updates `vitest` from 3.2.7 to 5.0.0-rc.4 - [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/v5.0.0-rc.4/packages/vitest) Updates `@vitest/ui` from 3.2.7 to 5.0.0-rc.4 - [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/v5.0.0-rc.4/packages/ui) --- updated-dependencies: - dependency-name: vitest dependency-version: 5.0.0-rc.4 dependency-type: direct:development - dependency-name: "@vitest/ui" dependency-version: 5.0.0-rc.4 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Contributor
Author
|
Superseded by #1154. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/src/App/multi-170fc8f861
branch
September 8, 2026 20:57
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
Vitest 5 RC introduces a Node engine requirement (>=22.12) that conflicts with the project’s current Node 20 runtime (e.g., Dockerfile), and there is also an override/version-range mismatch (picomatch) introduced by the upgrade.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
This PR updates the frontend app’s test tooling by bumping vitest and @vitest/ui together in src/App to the 5.0.0-rc.4 release candidate.
Changes:
- Bump
vitestfrom^3.2.6to^5.0.0-rc.4 - Bump
@vitest/uifrom^3.2.6to^5.0.0-rc.4 - Refresh
package-lock.jsonto reflect the new Vitest dependency graph
File summaries
| File | Description |
|---|---|
| src/App/package.json | Updates devDependencies to Vitest 5 RC and related UI package. |
| src/App/package-lock.json | Updates the resolved dependency tree and metadata for the Vitest 5 RC upgrade. |
Review details
Files not reviewed (1)
- src/App/package-lock.json: Generated file
Suppressed comments (1)
src/App/package.json:76
vitest@5depends onpicomatch: ^4.0.7(seepackage-lock.json), but this package.json forcespicomatchto4.0.4viaoverrides, which is outside that range. This can lead to dependency resolution warnings and potential runtime issues if Vitest relies on changes added in 4.0.7+. Either update the override to a compatible version or remove it if it’s no longer needed.
"vitest": "^5.0.0-rc.4"
},
"overrides": {
"minimatch": "3.1.5",
"vite": "7.3.5",
- Files reviewed: 1/2 changed files
- Comments generated: 2
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
9968
to
9970
| "engines": { | ||
| "node": "^18.0.0 || ^20.0.0 || >=22.0.0" | ||
| "node": "^22.12.0 || ^24.0.0 || >=26.0.0" | ||
| }, |
Comment on lines
70
to
+72
| "typescript": "^5.8.3", | ||
| "vite": "7.3.5", | ||
| "vitest": "^3.2.6" | ||
| "vitest": "^5.0.0-rc.4" |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps vitest and @vitest/ui. These dependencies needed to be updated together.
Updates
vitestfrom 3.2.7 to 5.0.0-rc.4Release notes
Sourced from vitest's releases.
... (truncated)
Commits
897f51fchore: release v5.0.0-rc.4 (#11107)1339b06chore(deps): update all non-major dependencies (#11104)51e9494feat!: parse files statically in vitest list by default (#11088)2122ffdfix: propagate --maxWorkers to projects (#11102)dc10f5ffix(browser): report the action error when a task times out (#11101)d4fe198feat: promote clearCache out of experimental (#11086)3f2ddc2fix(vm): link module graphs one at a time (#11096)848d724fix: don't duplicteoxc.targetif user provides a custom array (#11095)7db80dcchore: release v5.0.0-rc.3 (#11089)b628cb6feat: promote parseSpecifications out of experimental (#11087)Updates
@vitest/uifrom 3.2.7 to 5.0.0-rc.4Release notes
Sourced from @vitest/ui's releases.
... (truncated)
Commits
897f51fchore: release v5.0.0-rc.4 (#11107)1339b06chore(deps): update all non-major dependencies (#11104)58f02aefeat(ui): add link to open playwright trace (#11059)602d215fix(ui): add suite level report view (#11038)7db80dcchore: release v5.0.0-rc.3 (#11089)3cd019afix(ui): persist trace step-iframe split pane sizes (#11027)732df2cfix(deps): update all non-major dependencies (#11043)cd63e9efeat(ui): toggle trace target highlight (#11049)3069e59feat(ui): persist trace view selection in URL (#10981)1bbc278fix(browser): preserve trace popover state (fix #10906) (#11021)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)You can disable automated security fix PRs for this repo from the Security Alerts page.