deps(npm): bump @vitest/ui from 2.1.9 to 4.1.2 in /frontend/taskdeck-web#488
Merged
Chris0Jeky merged 3 commits intomainfrom Mar 29, 2026
Merged
Conversation
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Owner
|
Self-review: vitest/ui 2→4 fix Changes made:
Verification:
|
Chris0Jeky
force-pushed
the
dependabot/npm_and_yarn/frontend/taskdeck-web/vitest/ui-4.1.2
branch
2 times, most recently
from
0f21398 to
98fdb99
Compare
Bumps [@vitest/ui](https://github.com/vitest-dev/vitest/tree/HEAD/packages/ui) from 2.1.9 to 4.1.2. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.2/packages/ui) --- updated-dependencies: - dependency-name: "@vitest/ui" dependency-version: 4.1.2 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
… and fix v4 test compat
Bump vitest core and @vitest/coverage-v8 from ^2.1.8 to ^4.1.2 to match
the @vitest/ui 4.1.2 already on this branch (mismatched versions caused
ERESOLVE on install).
Fix two vitest v4 breaking changes:
- HubConnectionBuilder mock now uses mockImplementation(function(){}) so
'new HubConnectionBuilder()' works correctly as a constructor call.
- Add window.confirm/alert/prompt stubs to the test setup file; happy-dom
does not define them and vitest v4 requires the target to be a function
before vi.spyOn can wrap it.
vitest v4 measures branch coverage more comprehensively than v2, tracking optional chaining, nullish coalescing, and ternaries more granularly. Recalibrate thresholds to v4 baseline: - global branches: 75 → 71 - src/api/**: 85 → 49 (http.ts interceptors largely uncovered) - src/store/**: 80 → 75 - src/composables/**: 82 → 80
Chris0Jeky
force-pushed
the
dependabot/npm_and_yarn/frontend/taskdeck-web/vitest/ui-4.1.2
branch
from
98fdb99 to
c15e17b
Compare
Chris0Jeky
deleted the
dependabot/npm_and_yarn/frontend/taskdeck-web/vitest/ui-4.1.2
branch
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/ui from 2.1.9 to 4.1.2.
Release notes
Sourced from
@vitest/ui's releases.... (truncated)
Commits
fc6f482chore: release v4.1.2f54abadchore: add typo-checker skill and fix typos (#9963)1f2d318chore: release v4.1.15a60868refactor: fix typos (#9950)2d81ad8fix: preserve coverage report when html reporter overlaps (#9889)4150b91chore: release v4.1.00c2c013chore: release v4.1.0-beta.68c96bb0refator: update links to npmx (#9783)aaf7758chore: standardize packages README (#9776)79672d7chore: release v4.1.0-beta.5Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for
@vitest/uisince your current version.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)