-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
build(deps-dev): Bump the vitest group across 1 directory with 2 updates #161
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm 👍🏾
8a7af99
to
1333b4b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm 👍🏾
497520f
to
ef38ca0
Compare
Bumps the vitest group with 2 updates in the / directory: [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) and [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest). Updates `@vitest/coverage-v8` from 1.6.0 to 2.0.3 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v2.0.3/packages/coverage-v8) Updates `vitest` from 1.6.0 to 2.0.3 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v2.0.3/packages/vitest) --- updated-dependencies: - dependency-name: "@vitest/coverage-v8" dependency-type: direct:development update-type: version-update:semver-major dependency-group: vitest - dependency-name: vitest dependency-type: direct:development update-type: version-update:semver-major dependency-group: vitest ... Signed-off-by: dependabot[bot] <[email protected]>
cba689c
to
03968b6
Compare
Signed-off-by: flex-development[bot] <148604919+flex-development[bot]@users.noreply.github.com>
Superseded by #167. |
This pull request has been automatically locked since there has not been any recent |
Bumps the vitest group with 2 updates in the / directory: @vitest/coverage-v8 and vitest.
Updates
@vitest/coverage-v8
from 1.6.0 to 2.0.3Release notes
Sourced from
@vitest/coverage-v8
's releases.... (truncated)
Commits
81b8d67
chore: release v2.0.399a12ae
chore: release v2.0.280a43d5
fix(browser): inline pretty-format and replace picocolors with tinyrainbow (#...16eb6c8
chore: release v2.0.11b150a3
chore: release v2.0.05611895
chore: release v2.0.0-beta.13368c137
fix(coverage): remove work-around for implicitelse
(#6014)05d5f38
chore(deps): update all non-major dependencies (#5957)169bc1f
fix(coverage): support overridingexclude
(#5997)cd9cc6b
chore: release v2.0.0-beta.12Updates
vitest
from 1.6.0 to 2.0.3Release notes
Sourced from vitest's releases.
... (truncated)
Commits
81b8d67
chore: release v2.0.309dc75c
chore(deps): update dependency@edge-runtime/vm
to v4 (#6047)f851982
fix:--inspect-brk
stop on Windows (#6110)99a12ae
chore: release v2.0.280a43d5
fix(browser): inline pretty-format and replace picocolors with tinyrainbow (#...7012f8c
docs: add env documentation (#6063)16eb6c8
chore: release v2.0.14b03e72
fix(browser): correctly inherit browser config in a workspace (#6054)4d5597d
fix(vitest): print only running files, not every file (#6052)1b150a3
chore: release v2.0.0Dependabot 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 <dependency name> major version
will 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 version
will 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