This repository has been archived by the owner on Apr 11, 2024. It is now read-only.
Bump vitest and @vitest/coverage-v8 #152
Closed
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
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
the
dependencies
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/vitest-and-vitest/coverage-v8-1.4.0
branch
2 times, most recently
from
c61e268 to
7c24900
Compare
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/vitest-and-vitest/coverage-v8-1.4.0
branch
3 times, most recently
from
a829b07 to
e292721
Compare
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.4.0 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v1.4.0/packages/vitest) Updates `@vitest/coverage-v8` from 0.34.6 to 1.4.0 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v1.4.0/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] <[email protected]>
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/vitest-and-vitest/coverage-v8-1.4.0
branch
from
e292721 to
b63a943
Compare
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.4.0Release notes
Sourced from vitest's releases.
... (truncated)
Commits
a8da192chore: release v1.4.0d7e8b53feat(config): deprecatecache.diroption (#5229)c652148chore: remove unused propertyce5ca6bfix(vitest): logs inbeforeAllandafterAll(#5288)51d1d47fix(vitest): correctly override api with --no-api flag (#5386)efe441fchore: guard try/catch in websocket reporter07ec377fix(coverage): preventreportsDirectoryfrom removing user's project (#5376)38119b7fix(vitest): ignore timeout on websocket reporter rpce77c553fix:--inspect-brkto pause before execution (#5355)d627e20feat: add a flag to include test location in tasks (#5342)Maintainer changes
This version was pushed to npm by vitestbot, a new releaser for vitest since your current version.
Updates
@vitest/coverage-v8from 0.34.6 to 1.4.0Release notes
Sourced from
@vitest/coverage-v8's releases.... (truncated)
Commits
a8da192chore: release v1.4.0600b44dfeat(coverage): support--changedoption (#5314)6eda473fix(coverage): respect source maps of pre-transpiled sources (#5367)c3eb8defix(coverage): v8 to ignore type-only files (#5328)074450echore(deps): updateistanbul-lib-source-mapsto v5 (#5304)d68a739fix(coverage): expensive regexp hangs v8 report generation (#5259)e5114abchore: release v1.3.1a280451fix(coverage): ignore generated TS decorators (#5206)c692f76refactor(coverage): move common parts tovitestpackage (#5236)bb2af3bchore: release v1.3.0Maintainer changes
This version was pushed to npm by vitestbot, a new releaser for
@vitest/coverage-v8since your current version.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 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)