chore(deps-dev): bump vitest from 4.1.10 to 4.1.11 - #2714
dependabot[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Stale comment
Security review
No medium, high, or critical findings.
This Dependabot PR only bumps the devDependency
vitestfrom 4.1.10 to 5.0.0 in six packages (api-client,api-gen,cms-base-layer,composables,helpers,nuxt-module) and updatespnpm-lock.yaml. Lockfile integrity forvitest@5.0.0and@vitest/mocker@5.0.0matches the npm registry. No application or runtime code changed.Advisory check: GHSA-82fw-gwwq-j7x9 (CVE-2026-84373, path traversal via
@vitest/mockerredirect mocks) is fixed in 5.0.0. It is not reachable here: this repo does not use Vitest browser mode,@vitest/ui, or the publicmockerPlugin/interceptorPluginexports. Other 5.0.0-beta browser-mode issues (CDP RCE,otelCarrierXSS, provider-command file-gate bypass) were patched before the 5.0.0 stable release.No prior automation security threads to re-validate. Slack summary was not posted (post tool is not configured).
Sent by Cursor Automation: Review pull requests for exploitable security issues and flag only validated findings before merge
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 4.1.10 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: 5.0.0 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
21dabac to
2eb07d7
Compare
There was a problem hiding this comment.
Security review
No medium, high, or critical findings.
This Dependabot synchronize only bumps the devDependency vitest from 4.1.10 to 4.1.11 in six packages (api-client, api-gen, cms-base-layer, composables, helpers, nuxt-module) and refreshes pnpm-lock.yaml. No application or runtime code changed. Lockfile integrity for vitest@4.1.11 and @vitest/mocker@4.1.11 matches the npm registry.
Advisory check: GHSA-82fw-gwwq-j7x9 (CVE-2026-84373, path traversal via @vitest/mocker redirect mocks) is fixed in 4.1.11. The repo already overrides vitest / @vitest/mocker <4.1.11 to 4.1.11; this PR aligns the declared versions. The advisory is also not reachable here: Vitest configs use Node or happy-dom, not browser mode, and there is no use of the public mockerPlugin / interceptorPlugin exports.
Prior automation review (opened, then targeting a 5.0.0 bump) had no finding threads to re-validate. Slack summary was not posted (post tool is not configured).
Sent by Cursor Automation: Review pull requests for exploitable security issues and flag only validated findings before merge


Bumps vitest from 4.1.10 to 4.1.11.
Release notes
Sourced from vitest's releases.
Commits
9bd8d46chore: release v4.1.11 (#10995)9851dbcfix(browser): trigger playwright/chromium gc on lower disk availability [back...