Skip to content

Bump vitest from 1.3.1 to 1.5.3#82

Closed
dependabot[bot] wants to merge 1 commit intostart-branchfrom
dependabot/npm_and_yarn/vitest-1.5.3
Closed

Bump vitest from 1.3.1 to 1.5.3#82
dependabot[bot] wants to merge 1 commit intostart-branchfrom
dependabot/npm_and_yarn/vitest-1.5.3

Conversation

@dependabot
Copy link
Contributor

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

Bumps vitest from 1.3.1 to 1.5.3.

Release notes

Sourced from vitest's releases.

v1.5.3

   🐞 Bug Fixes

    View changes on GitHub

v1.5.2

   🐞 Bug Fixes

    View changes on GitHub

v1.5.1

   🚀 Features

  • api: startVitest() to accept stdout and stdin  -  by @​AriPerkkio in vitest-dev/vitest#5493 (780b1)
    • This is listed as a feature, but it doesn't increase the minor version because startVitest API is experimental and doesn't follow semver.

   🐞 Bug Fixes

    View changes on GitHub

v1.5.0

   🚀 Features

... (truncated)

Commits
  • a52964b chore: release v1.5.3
  • 200609c fix(reporter): use default error formatter for JUnit (#5629)
  • 48fba19 fix: use package.json name for a workspace project if not provided (#5608)
  • 7c993e9 test: standardising internal test (#5600)
  • 81f57f4 chore: release v1.5.2
  • 1be4510 chore: release v1.5.1
  • f1bec62 refactor: remove VitestCache.clearCache method (#5602)
  • 780b187 feat(api): startVitest() to accept stdout and stdin (#5493)
  • 2b3fc0f docs: fix cli-table generator
  • 597e0c2 docs: generate CLI table automatically (#5588)
  • Additional commits viewable in compare view

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)

Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 1.3.1 to 1.5.3.
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v1.5.3/packages/vitest)

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

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label May 1, 2024
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Jun 1, 2024

Superseded by #86.

@dependabot dependabot bot closed this Jun 1, 2024
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/vitest-1.5.3 branch June 1, 2024 06:48
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.

0 participants