chore(deps): bump vitest from 3.2.7 to 5.0.0 - #438
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
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 3.2.7 to 5.0.0. - [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.0/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 4.1.11 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/vitest-4.1.11
branch
from
September 10, 2026 21:27
0d67bed to
6f773f0
Compare
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
mohanagy
added a commit
that referenced
this pull request
Sep 11, 2026
Vitest 5 applies AST-aware remapping unconditionally, attributing functions and branches differently from Vitest 3. With identical tests and unchanged source, the measured figures moved in both directions — upstream-process-manager functions 100 -> 89.84 and redact branches 94.69 -> 87.17, but secret-provider-availability branches 81.57 -> 84.21 and secret-resolver functions 86.66 -> 89.47 — so this is a measurement change, not a coverage regression. Confirmed by running coverage on development (Vitest 3), where the same tests meet every threshold. Vitest 5 removed the experimental opt-out, so the previous measurement cannot be restored. Recalibrated the seven breached function and branch thresholds to measured actuals with a small margin, preserving the ratchet going forward. Line thresholds were unaffected and are unchanged. Refs #435, #436, #437, #438, #445 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
mohanagy
added a commit
that referenced
this pull request
Sep 11, 2026
Supersedes #445, #438, #437, #436, #435, none of which could go green alone. Vitest 3.2.7 -> 5.0.0 with @vitest/coverage-v8 and vite as an explicit devDependency (Vitest 5 declares vite a non-optional peer). @types/node 22 -> 26, @hono/node-server 2.0.10 -> 2.1.1, esbuild 0.28.1 -> 0.28.2, eslint 10.8.0 -> 10.10.0, typescript-eslint 8.65.0 -> 8.70.0. Both the production-only and full npm audits now report zero. @types/node 26 added a throwIfNoEntry overload to stat(), so Awaited<ReturnType<typeof stat>> resolves to Stats | BigIntStats | undefined and keyof of that union is never. Replaced the idiom with the concrete Stats type in the three files using it. Vitest 4 removed test.poolOptions and promoted its contents to top-level options. Vitest 5 applies AST-aware remapping unconditionally, so function and branch figures are not comparable across the migration; thresholds recalibrated to measured actuals with line thresholds unchanged. zod 4.2.0 -> 4.6.2 deliberately held: the evidence-pinned bundled fixture embeds zod, so bumping it invalidates the sha256 that the named-host evidence ledger pins. Lock-only hold; the declared ^4.2.0 range is unchanged. Refs #435, #436, #437, #438, #445 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Owner
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.0.
Release notes
Sourced from vitest's releases.
... (truncated)
Commits
f441c6fchore: release v5.0.0 (#11130)d46a747fix: treat test.describe as a suite during static collection (#11128)584cf30fix: add a warning if inline project has duplicate plugins due to unexpected ...f08ce4bfix: apply queued mocks from doMock() in queue order (fixes #10706) (#11127)897f51fchore: release v5.0.0-rc.4 (#11107)1339b06chore(deps): update all non-major dependencies (#11104)51e9494feat!: parse files statically in vitest list by default (#11088)2122ffdfix: propagate --maxWorkers to projects (#11102)dc10f5ffix(browser): report the action error when a task times out (#11101)d4fe198feat: promote clearCache out of experimental (#11086)