chore(deps-dev): bump vitest from 3.2.6 to 4.1.11 - #1121
Open
dependabot[bot] wants to merge 1 commit into
Open
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) from 3.2.6 to 4.1.11. - [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/v4.1.11/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 4.1.11 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| "typescript": "^5.8.3", | ||
| "typescript-eslint": "^8.62.1", | ||
| "vitest": "^3.2.4", | ||
| "vitest": "^4.1.11", |
There was a problem hiding this comment.
Vitest 4 no longer installs vite-node, but packages/evals/test/eval-durable.test.ts still resolves vite-node/vite-node.mjs through Vitest before starting a child process. Running the @ultrafuzz/evals test suite will therefore fail with a module-resolution error. Update the helper to use an execution path supported by Vitest 4.
Prompt To Fix With AI
This is a comment left during a code review.
Path: package.json
Line: 49
Comment:
**Vitest Upgrade Breaks Eval Tests**
Vitest 4 no longer installs `vite-node`, but `packages/evals/test/eval-durable.test.ts` still resolves `vite-node/vite-node.mjs` through Vitest before starting a child process. Running the `@ultrafuzz/evals` test suite will therefore fail with a module-resolution error. Update the helper to use an execution path supported by Vitest 4.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
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 from 3.2.6 to 4.1.11.
Release notes
Sourced from vitest's releases.
... (truncated)
Commits
9bd8d46chore: release v4.1.11 (#10995)9851dbcfix(browser): trigger playwright/chromium gc on lower disk availability [back...db616d2chore: release v4.1.10 (#10718)bae52b5fix(vm): fix external module resolve error with deps optimizer query for enco...a7a61e7chore: release v4.1.9 (#10598)934b0f5fix(pool): prevent test run hang on worker crash (#10543) [backport to v4] (#...7fb2965fix(browser): wait for orchestrator readiness before resolving browser sessio...a518019fix: fiximportOriginalwith optimizer and query import [backport to v4] (#...e61f2ddchore: release v4.1.8e4067b3fix(browser): disable clientcdpAPI whenallowWrite/allowExec: false[ba...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.
Greptile Summary
This PR upgrades the repository's shared Vitest development dependency from 3.2.6 to 4.1.11 and refreshes its transitive lockfile entries.
vite-nodedependency, which conflicts with an existing eval test helper that directly resolves its executable.Confidence Score: 4/5
This PR is not safe to merge until the eval test helper is migrated away from the removed
vite-nodedependency.The upgraded dependency graph no longer installs
vite-node, while the eval suite synchronously resolves its executable before spawning a child process, causing that suite to fail.Files Needing Attention: package.json, packages/evals/test/eval-durable.test.ts
Important Files Changed
vite-nodedependency.vite-node.Prompt To Fix All With AI
Reviews (1): Last reviewed commit: "chore(deps-dev): bump vitest from 3.2.6 ..." | Re-trigger Greptile