chore(deps-dev): bump vitest from 4.1.9 to 4.1.11 - #9
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
dependabot
Bot
added
dependencies
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/vitest-4.1.11
branch
from
September 15, 2026 19:27
f40b9be to
226c2b7
Compare
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 4.1.9 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
force-pushed
the
dependabot/npm_and_yarn/vitest-4.1.11
branch
from
September 22, 2026 16:16
226c2b7 to
04e84e2
Compare
This branch has not been deployed
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 4.1.9 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...db616d2chore: release v4.1.10 (#10718)bae52b5fix(vm): fix external module resolve error with deps optimizer query for enco...Note
Low Risk
Dev-only lockfile bump with no production or app code changes; main impact is test/CI behavior from vitest patch releases.
Overview
Updates
pnpm-lock.yamlonly, resolving vitest from 4.1.9 to 4.1.11 (still within the existing^4.1.4range inpackage.json). All@vitest/*packages move to 4.1.11 in lockstep.The lockfile also refreshes transitive tooling used by vitest/vite: rolldown (1.1.3 → 1.1.5), lightningcss (1.32.0 → 1.33.0), postcss, picomatch, es-module-lexer, and related bindings—mostly version/hash churn, not application source changes.
4.1.10–4.1.11 bring test-runner fixes worth knowing for CI: restored global concurrency limits for test lifecycle, tighter mocker redirect behavior (fs allowlist), browser iframe URL encoding, and filesystem checks in browser builtin commands.
Reviewed by Cursor Bugbot for commit 04e84e2. Bugbot is set up for automated code reviews on this repo. Configure here.