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

Bump vitest from 0.34.6 to 1.3.1 #71

Merged
merged 1 commit into from
Mar 1, 2024

Conversation

dependabot[bot]
Copy link
Contributor

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

Bumps vitest from 0.34.6 to 1.3.1.

Release notes

Sourced from vitest's releases.

v1.3.1

   🚀 Features

   🐞 Bug Fixes

    View changes on GitHub

v1.3.0

🚀 Features

🐞 Bug Fixes

... (truncated)

Commits
  • e5114ab chore: release v1.3.1
  • c793a13 feat(vitest): expose parseCLI method (#5248)
  • 2f755f0 docs: fix defaults in JSDocs to be more accurate (#5196)
  • 5376d5b fix(ui): auto reload coverage iframe after test run (#5242)
  • 671cbcd chore: update license
  • c692f76 refactor(coverage): move common parts to vitest package (#5236)
  • bb2af3b chore: release v1.3.0
  • bc5b2d0 fix: Prevent merging of poolOptions (#5221)
  • 1aecd65 fix(vitest): fix optimizeDeps.disabled warnings on Vite 5.1 (#5215)
  • b3182e0 chore: pass down --update flag to the project config
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by vitestbot, a new releaser for vitest since your current version.


Dependabot compatibility score

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 this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Mar 1, 2024
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 0.34.6 to 1.3.1.
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v1.3.1/packages/vitest)

---
updated-dependencies:
- dependency-name: vitest
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/vitest-1.3.1 branch from 8644e8e to 4027a49 Compare March 1, 2024 18:37
@guiyom-e guiyom-e merged commit ff324e6 into start-branch Mar 1, 2024
1 check passed
@guiyom-e guiyom-e deleted the dependabot/npm_and_yarn/vitest-1.3.1 branch March 1, 2024 18:38
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