build(deps-dev): bump the vitest group across 1 directory with 3 updates #439
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
scope:dependencies
Bumps the vitest group with 3 updates in the / directory: [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8), [@vitest/expect](https://github.com/vitest-dev/vitest/tree/HEAD/packages/expect) and [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest). Updates `@vitest/coverage-v8` from 1.0.0-beta.3 to 1.6.0 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v1.6.0/packages/coverage-v8) Updates `@vitest/expect` from 1.0.0-beta.3 to 1.6.0 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v1.6.0/packages/expect) Updates `vitest` from 1.0.0-beta.3 to 1.6.0 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v1.6.0/packages/vitest) --- updated-dependencies: - dependency-name: "@vitest/coverage-v8" dependency-type: direct:development update-type: version-update:semver-minor dependency-group: vitest - dependency-name: "@vitest/expect" dependency-type: direct:development update-type: version-update:semver-minor dependency-group: vitest - dependency-name: vitest dependency-type: direct:development update-type: version-update:semver-minor dependency-group: vitest ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/vitest-6afd0c5b8c
branch
from
bd6d249
to
0607431
Compare
Signed-off-by: flex-development[bot] <148604919+flex-development[bot]@users.noreply.github.com>
|
Superseded by #471. |
|
This pull request has been automatically locked since there has not been any recent |
flex-development
bot
added
the
status:stale
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 the vitest group with 3 updates in the / directory: @vitest/coverage-v8, @vitest/expect and vitest.
Updates
@vitest/coverage-v8from 1.0.0-beta.3 to 1.6.0Release notes
Sourced from
@vitest/coverage-v8's releases.... (truncated)
Commits
6b29f3dchore: release v1.6.0c9883f3fix(coverage): applyvite-node's wrapper only to executed files (#5642)a52964bchore: release v1.5.381f57f4chore: release v1.5.21be4510chore: release v1.5.180265b4fix(coverage):thresholdsto compare files relative to root (#5574)ea3c16efix(coverage): prevent crash whencleanOnRerunis disabled (#5540)9e7a01cchore: release v1.5.010b8971feat(coverage): v8 to ignore empty lines, comments, types (#5457)a8da192chore: release v1.4.0Maintainer changes
This version was pushed to npm by vitestbot, a new releaser for
@vitest/coverage-v8since your current version.Updates
@vitest/expectfrom 1.0.0-beta.3 to 1.6.0Release notes
Sourced from
@vitest/expect's releases.... (truncated)
Commits
6b29f3dchore: release v1.6.0a52964bchore: release v1.5.330e5dc1fix: backport jest iterable equality within object (#5621)81f57f4chore: release v1.5.2ce36845fix: check for null before storing in weakmap1be4510chore: release v1.5.19e6417cfix(expect): fixtoEqualandtoMatchObjectwith circular references (#5535)9e7a01cchore: release v1.5.09927639feat: remove unrelated noise from diff for toMatchObject() (#5364)674851cfix: the value received by toMatch should be a string (#5428)Maintainer changes
This version was pushed to npm by vitestbot, a new releaser for
@vitest/expectsince your current version.Updates
vitestfrom 1.0.0-beta.3 to 1.6.0Release notes
Sourced from vitest's releases.
... (truncated)
Commits
6b29f3dchore: release v1.6.0f8d3d22feat(benchmark): support comparing benchmark result (#5398)21e58bdfeat(browser): allow injecting scripts (#5656)30f728bfeat: custom "snapshotEnvironment" option (#5449)2f91322feat(reporter): supportincludeConsoleOutputandaddFileAttributein juni...c571276perf: unnecessary rpc call when coverage is disabled (#5658)bdce0a2feat: support standalone mode (#5565)40c299ffix: don't panic on empty files in node_modulesc9e68cefix: hash the name of the file when caching (#5654)f5faf42fix: callresolveId('vitest')afterbuildStart(#5646)Maintainer changes
This version was pushed to npm by vitestbot, a new releaser for vitest since 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 <dependency name> major versionwill 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 versionwill 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