Skip to content

Update dependency vitest to v4.1.11 [SECURITY] (2.x) #702

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
renovate wants to merge 1 commit into
base: 2.x
Choose a base branch
from
Open

Update dependency vitest to v4.1.11 [SECURITY] (2.x) #702

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion packages/eslint-plugin-ui/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@
"esbuild": "0.27.4",
"eslint": "9.34.0",

@github-actions github-actions Bot Oct 28, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

issue: Synchronize the lockfile with the Vitest update

package-lock.json still records packages/eslint-plugin-ui with vitest at 4.1.2, while this manifest requires 4.1.11. A clean npm ci installation therefore detects an out-of-sync workspace lockfile and fails. Regenerate and commit package-lock.json so it records Vitest 4.1.11 and its resolved dependency tree.

Confidence: high.

Reviewed by @weareikko/code-review v0.11.1 for commit 16624a4.

"typescript": "6.0.2",
"vitest": "4.1.2"
"vitest": "4.1.11"

@github-actions github-actions Bot Nov 3, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

issue: Regenerate the lockfile for Vitest 4.1.11

package-lock.json still records packages/eslint-plugin-ui with vitest: 4.1.2 and resolves node_modules/vitest plus @vitest/mocker at 4.1.2. A locked install therefore retains the vulnerable version and does not apply the security update. Regenerate and commit package-lock.json so its workspace entry and resolved Vitest tree match 4.1.11.

Confidence: high.

Reviewed by @weareikko/code-review v0.11.1 for commit d6c683e.

},
"dependencies": {
"@oxlint/plugins": "1.63.0"
Expand Down
Loading