Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps-dev): bump vitest and @vitest/coverage-v8 #449

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 1, 2024

Bumps vitest and @vitest/coverage-v8. These dependencies needed to be updated together.
Updates vitest from 0.34.6 to 1.1.1

Release notes

Sourced from vitest's releases.

v1.1.1

   🐞 Bug Fixes

    View changes on GitHub

v1.1.0

   🚀 Features

   🐞 Bug Fixes

    View changes on GitHub

v1.0.4

The previous release was built incorrectly and didn't include the performance fix. This release fixes that.

   🐞 Bug Fixes

... (truncated)

Commits
  • c8abbc1 chore: release v1.1.1
  • 2baea35 fix(vitest): show beforeAll/afterAll errors in junit reporter (#4819)
  • 7e6a62a fix: match jest json output by making json reporter output ndjson-compatible ...
  • 5053a5d fix: correct option name --no-parallelism (#4831)
  • 06c14f7 fix(vitest): fix file snapshots in skipped suites considered obsolete (#4795)
  • 8ddb494 chore: always externalize vitest (#4816)
  • 8f6225b fix: don't fail if inline: true is set (#4815)
  • ee8b46d fix: don't crash when using happy-dom or jsdom environment on Yarn PnP worksp...
  • 957daa3 fix(vitest): initialize snapshot state only once for each file suite (#4796)
  • cf53d4b fix(vm-threads): tests not cancelled on key press, cancelled tests shown twic...
  • Additional commits viewable in compare view

Updates @vitest/coverage-v8 from 0.34.6 to 1.1.1

Release notes

Sourced from @​vitest/coverage-v8's releases.

v1.1.1

   🐞 Bug Fixes

    View changes on GitHub

v1.1.0

   🚀 Features

   🐞 Bug Fixes

    View changes on GitHub

v1.0.4

The previous release was built incorrectly and didn't include the performance fix. This release fixes that.

   🐞 Bug Fixes

... (truncated)

Commits
  • c8abbc1 chore: release v1.1.1
  • 9497f48 chore: release v1.1.0
  • 66933c3 chore: release v1.0.4
  • 7c19664 chore: release v1.0.3
  • 7006bb3 chore: release v1.0.2
  • 0802167 chore: release v1.0.1
  • 420707f fix: bump vitest packages peerDependencies versions (#4654)
  • 34517ce chore: release v1.0.0
  • 4166c41 fix(coverage): improve memory usage by writing temporary files on file system...
  • b766d34 chore: release v1.0.0-beta.6
  • Additional commits viewable in compare view

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

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>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jan 1, 2024
@dependabot dependabot bot requested a review from erunion January 1, 2024 01:13
@erunion erunion merged commit 9994486 into main Jan 1, 2024
6 checks passed
@erunion erunion deleted the dependabot/npm_and_yarn/vitest-and-vitest/coverage-v8-1.1.1 branch January 1, 2024 19:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant