-
-
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 3 updates #778
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
added
scope:dependencies
dependency updates
type:build
changes to the build system or external dependencies
labels
Jan 17, 2025
unicornware
previously approved these changes
Jan 17, 2025
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 👍🏾
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/vitest-b8cf70308e
branch
2 times, most recently
from
January 17, 2025 22:20
7348458
to
2ac5612
Compare
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/ui](https://github.com/vitest-dev/vitest/tree/HEAD/packages/ui) and [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest). Updates `@vitest/coverage-v8` from 3.0.0-beta.3 to 3.0.2 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v3.0.2/packages/coverage-v8) Updates `@vitest/ui` from 3.0.0-beta.3 to 3.0.2 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v3.0.2/packages/ui) Updates `vitest` from 3.0.0-beta.3 to 3.0.2 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v3.0.2/packages/vitest) --- updated-dependencies: - dependency-name: "@vitest/coverage-v8" dependency-type: direct:development update-type: version-update:semver-patch dependency-group: vitest - dependency-name: "@vitest/ui" dependency-type: direct:development update-type: version-update:semver-patch dependency-group: vitest - dependency-name: vitest dependency-type: direct:development update-type: version-update:semver-patch dependency-group: vitest ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/vitest-b8cf70308e
branch
from
January 20, 2025 23:11
266b4b5
to
910e139
Compare
Signed-off-by: flex-development[bot] <148604919+flex-development[bot]@users.noreply.github.com>
unicornware
approved these changes
Jan 20, 2025
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 👍🏾
Superseded by #783. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
scope:dependencies
dependency updates
type:build
changes to the build system or external dependencies
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/ui and vitest.
Updates
@vitest/coverage-v8
from 3.0.0-beta.3 to 3.0.2Release notes
Sourced from
@vitest/coverage-v8
's releases.... (truncated)
Commits
f17918a
chore: release v3.0.256c5018
chore: release v3.0.1537fa5e
fix(deps): update all non-major dependencies (#7147)01600e0
chore: release v3.0.08cab960
fix: colors onforks
pool (#7090)57b671d
chore: release v3.0.0-beta.474dbe03
fix(deps): update dependency pathe to v2 (#7181)cb6db13
fix(coverage): prevent crash when v8 incorrectly merges static_initializer's ...Updates
@vitest/ui
from 3.0.0-beta.3 to 3.0.2Release notes
Sourced from
@vitest/ui
's releases.... (truncated)
Commits
f17918a
chore: release v3.0.256c5018
chore: release v3.0.1537fa5e
fix(deps): update all non-major dependencies (#7147)01600e0
chore: release v3.0.0faca4de
fix(ui): add errors and draft state (*) to the code editor (#7044)8cab960
fix: colors onforks
pool (#7090)9175836
feat: add resolved project names to the reporter API (#7213)b307055
refactor: fix tsconfig file in ui (#7221)a942ea7
chore(ui): fix static ui client types (#7201)50cf61b
feat(ui): allow hide/show node_modules in module graph tab (#7217)Updates
vitest
from 3.0.0-beta.3 to 3.0.2Release notes
Sourced from vitest's releases.
... (truncated)
Commits
f17918a
chore: release v3.0.256c5018
chore: release v3.0.1755ecdf
Revert "fix: re-apply default conditions if using vite 6 or later (#7071)" (#...537fa5e
fix(deps): update all non-major dependencies (#7147)01600e0
chore: release v3.0.084287fc
fix: re-apply default conditions if using vite 6 or later (#7071)b526896
fix(coverage)!: always exclude test files (#7254)1c2b210
fix(api): don't report events duringvitest list
(#7257)80ce0e1
feat(api): add onBrowserInit event (#7255)003c0be
fix(watch): don't indicate exit when no matching files (#7246)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 <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