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/coverage-v8 from 1.0.4 to 1.3.0 #374

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 19, 2024

Bumps @vitest/coverage-v8 from 1.0.4 to 1.3.0.

Release notes

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

v1.3.0

🚀 Features

🐞 Bug Fixes

... (truncated)

Commits
  • bb2af3b chore: release v1.3.0
  • 2ee2317 ci: add publish workflow (#5168)
  • 68f5196 fix: requires fixed version across the monorepo (#5208)
  • 5749d2c fix(coverage): .tmp directory conflicts with --shard option (#5184)
  • 7a31a1a chore(deps): update dependency @​antfu/eslint-config to v2 (#5153)
  • b1462a4 chore: release v1.2.2
  • d53b858 fix(coverage): remove coverage/.tmp files after run (#5008)
  • 6421c27 chore: release v1.2.1
  • 4b41131 fix(coverage): thresholds.autoUpdate to work with arrow function configurat...
  • b561c32 chore: release v1.2.0
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by vitestbot, a new releaser for @​vitest/coverage-v8 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)

Bumps [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) from 1.0.4 to 1.3.0.
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v1.3.0/packages/coverage-v8)

---
updated-dependencies:
- dependency-name: "@vitest/coverage-v8"
  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 Feb 19, 2024
Copy link
Contributor Author

dependabot bot commented on behalf of github Feb 26, 2024

Superseded by #380.

@dependabot dependabot bot closed this Feb 26, 2024
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/vitest/coverage-v8-1.3.0 branch February 26, 2024 11:06
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