chore(deps-dev): bump vitest from 3.2.7 to 5.0.1 - #139
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
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/vitest-5.0.1
branch
from
September 21, 2026 14:21
8729dfd to
4eeb453
Compare
alperhankendi
added a commit
that referenced
this pull request
Sep 21, 2026
vitest and @vitest/coverage-v8 must move together: #139 bumped vitest alone and left coverage-v8 at 3.2.7, which resolves `vitest/coverage` - a subpath vitest 5 no longer exports - and crashed every unit run with ERR_PACKAGE_PATH_NOT_EXPORTED. #142 is the same split in reverse. One real breaking change surfaced: cli-router mocks UpdateCommand with an arrow function, but cli-router.ts calls `new UpdateCommand(...)`. Arrow functions have no [[Construct]] slot; vitest 3 tolerated this, vitest 5 does not. Swapped in a regular function so the mock stays constructible. Local run on Windows: 1219/1219 unit tests pass, typecheck clean across all six packages. The one remaining full-suite failure is privacy-zero-leakage hitting EPERM while unlinking its Windows temp dir - it passes in isolation and is platform cleanup, not a vitest regression. Pushing to confirm on Linux.
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 3.2.7 to 5.0.1. - [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/v5.0.1/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 5.0.1 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/vitest-5.0.1
branch
from
September 21, 2026 14:34
4eeb453 to
2f361ad
Compare
alperhankendi
added a commit
that referenced
this pull request
Sep 21, 2026
* test(deps): move workspace to vitest 5 vitest and @vitest/coverage-v8 must move together: #139 bumped vitest alone and left coverage-v8 at 3.2.7, which resolves `vitest/coverage` - a subpath vitest 5 no longer exports - and crashed every unit run with ERR_PACKAGE_PATH_NOT_EXPORTED. #142 is the same split in reverse. One real breaking change surfaced: cli-router mocks UpdateCommand with an arrow function, but cli-router.ts calls `new UpdateCommand(...)`. Arrow functions have no [[Construct]] slot; vitest 3 tolerated this, vitest 5 does not. Swapped in a regular function so the mock stays constructible. Local run on Windows: 1219/1219 unit tests pass, typecheck clean across all six packages. The one remaining full-suite failure is privacy-zero-leakage hitting EPERM while unlinking its Windows temp dir - it passes in isolation and is platform cleanup, not a vitest regression. Pushing to confirm on Linux. * test(coverage): recalibrate src/core thresholds for coverage-v8 5 The v8 provider changed how it maps ranges to branches between 3.x and 5.x. Same source, same 1219 tests, different denominators for src/core: vitest 3 branches 1163/1300 = 89.46% statements 3155/3234 = 97.56% vitest 5 branches 1031/1198 = 86.06% statements 1814/1908 = 95.07% Per-file the shift is unmistakably measurement rather than lost coverage: masking-pipeline goes 12/12 -> 5/5, cluster-label-masker 21/21 -> 9/10, intent-filter 19/19 -> 11/12. Files that were fully covered still are; the provider just counts fewer branches and marks one of them uncovered. Writing tests to chase the old 88 would be aiming at an artifact. Branches drops to 85, preserving roughly the slack the old 88 gave against the 3.x baseline. Statements, functions and lines go 88/90/88 -> 92, since the actual 5.x numbers (95.07 / 95.80 / 96.89) clear that comfortably - so this is a recalibration, not a blanket loosening. Verified: threshold rejects at 87 (86.06% < 87%) and passes at 85, so the gate still enforces rather than trivially passing.
Owner
|
Kapatılıyor: #144 bu yükseltmeyi kapsıyor ve master'a merge edildi (
|
Contributor
Author
|
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. |
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 3.2.7 to 5.0.1.
Release notes
Sourced from vitest's releases.
... (truncated)
Commits
03630a5chore: release v5.0.1 (#11275)a47d790fix(fakeTimers): forcequeueMicrotaskandnextTickintoNotFake(#11261)2ce29d5fix: warn when deprecateddeps.optimizer.webis used (#11214)ccd6d05docs: fix typecheck exclude default in documentation (#11223)91ab158fix(doctor): measure vm pools for custom environments (#11212)23dda73fix: share the server on self-referencingextends(#11034)498fbe9fix: resolve ResolvedConfig exactOptionalPropertyTypes errors (#11175)115c3f6fix: correct typos in error message and comments (#11187)7361465fix: keep metadata file when clearing the cache (#11199)972e24bfix(browser): avoid double quotes inconfig.define(#11198)