Repository navigation
Bump vitest from 4.1.10 to 4.1.11 - #64
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
dependabot
Bot
added
dependencies
Owner
|
@dependabot recreate |
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>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/vitest-4.1.11
branch
from
October 2, 2026 10:01
d8ddd7d to
21d5f7e
Compare
Comprehensive-Jason
added a commit
that referenced
this pull request
Oct 2, 2026
….1.11 for the @vitest/mocker path-traversal advisory, and esbuild to ^0.28.2 so the lockfile installs under every npm (2026-10-02, replaces Dependabot PR #64). Vitest 4.1.11 brings vite 8.3.2, whose optional esbuild peer range is "^0.27.0 || ^0.28.0" and no longer covers our own esbuild 0.25.12. npm 10 (CI's Node 22) and npm 12 (local) resolve that unmet optional peer differently, so a lockfile written by one is rejected by the other with "Missing: esbuild@0.28.2 from lock file"; Dependabot's lockfile failed CI that way twice, including after a recreate. Raising our esbuild into vite's range leaves one copy that satisfies both, and this lockfile passes npm ci under npm 10.9.9 and npm 12.2.0. The release build is unaffected: built unminified with identical options, esbuild 0.25.12 and 0.28.2 produce a byte-identical bundle (329,029 bytes); the minified main.js differs by 13 bytes of minifier packing, and neither contains syntax above the es2018 target that issue #46's Android WebViews need. The ^4.1.11 floors also stop a fresh resolve landing back on the vulnerable version. Suite 2948 + 31 expected fail; tsc, eslint (src+test), knip, build green, each step checked for its own exit code
Author
|
Looks like vitest is up-to-date now, so this is no longer needed. |
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
1 participant
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.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...