build(deps-dev): bump vitest from 4.1.10 to 4.1.11 in /src/frontend - #1642
build(deps-dev): bump vitest from 4.1.10 to 4.1.11 in /src/frontend#1642dependabot[bot] wants to merge 1 commit into
Conversation
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: 4.1.11 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
🟢 Approval recommended
The change is a straightforward dev dependency patch bump with a consistent lockfile update and no detected incompatibilities within the reviewed diffs.
Pull request overview
This PR updates the frontend test runner dependency to the latest patch release of Vitest, keeping the src/frontend toolchain in sync with upstream bug fixes while refreshing the pnpm lockfile accordingly.
Changes:
- Bump
vitestdevDependency from^4.1.10to^4.1.11insrc/frontend/package.json. - Update
src/frontend/pnpm-lock.yamlto reflect Vitest 4.1.11 and resulting transitive dependency resolutions.
File summaries
| File | Description |
|---|---|
| src/frontend/pnpm-lock.yaml | Lockfile refresh for Vitest 4.1.11 and related transitive updates. |
| src/frontend/package.json | Updates Vitest devDependency version range to ^4.1.11. |
Review details
Files not reviewed (1)
- src/frontend/pnpm-lock.yaml: Generated file
- Files reviewed: 1/2 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
Tracked/superseded by #1645 — the [auto-sec] canonical remediation for the aspire.dev frontend npm security cluster, which folds this update in and clears all 12 open Dependabot alerts. Keeping this open until the canonical PR is confirmed green, then it will be closed as superseded. |
|
Superseded by #1645, the canonical [auto-sec] consolidation for /src/frontend npm dependencies. #1645 is open, mergeable, conflict-free, and CI-green (frontend build + all E2E suites pass), and it already includes this bump (regenerated pnpm-lock.yaml with public-registry tarballs + overrides clearing all Dependabot alerts). Closing per the automation closure gate; will be reopened if #1645 is not merged. |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
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...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.