Bump vitest and @vitest/coverage-v8 #75
Open
Conversation
This file contains 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
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) and [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8). These dependencies needed to be updated together. Updates `vitest` from 0.34.6 to 1.1.1 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v1.1.1/packages/vitest) Updates `@vitest/coverage-v8` from 0.34.6 to 1.1.1 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v1.1.1/packages/coverage-v8) --- updated-dependencies: - dependency-name: vitest dependency-type: direct:development update-type: version-update:semver-major - dependency-name: "@vitest/coverage-v8" dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #75 +/- ##
==========================================
- Coverage 81.83% 77.12% -4.71%
==========================================
Files 135 202 +67
Lines 17052 18093 +1041
Branches 974 1041 +67
==========================================
Hits 13955 13955
- Misses 3097 4071 +974
- Partials 0 67 +67 ☔ View full report in Codecov by Sentry. |
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 and @vitest/coverage-v8. These dependencies needed to be updated together.
Updates
vitestfrom 0.34.6 to 1.1.1Release notes
Sourced from vitest's releases.
... (truncated)
Commits
c8abbc1chore: release v1.1.12baea35fix(vitest): showbeforeAll/afterAllerrors in junit reporter (#4819)7e6a62afix: match jest json output by making json reporter output ndjson-compatible ...5053a5dfix: correct option name--no-parallelism(#4831)06c14f7fix(vitest): fix file snapshots in skipped suites considered obsolete (#4795)8ddb494chore: always externalize vitest (#4816)8f6225bfix: don't fail ifinline: trueis set (#4815)ee8b46dfix: don't crash when using happy-dom or jsdom environment on Yarn PnP worksp...957daa3fix(vitest): initialize snapshot state only once for each file suite (#4796)cf53d4bfix(vm-threads): tests not cancelled on key press, cancelled tests shown twic...Updates
@vitest/coverage-v8from 0.34.6 to 1.1.1Release notes
Sourced from
@vitest/coverage-v8's releases.... (truncated)
Commits
c8abbc1chore: release v1.1.19497f48chore: release v1.1.066933c3chore: release v1.0.47c19664chore: release v1.0.37006bb3chore: release v1.0.20802167chore: release v1.0.1420707ffix: bump vitest packagespeerDependenciesversions (#4654)34517cechore: release v1.0.04166c41fix(coverage): improve memory usage by writing temporary files on file system...b766d34chore: release v1.0.0-beta.6Dependabot 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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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)