deps(deps-dev): bump @vitest/coverage-v8 from 2.1.9 to 4.1.10 - #79
Closed
dependabot[bot] wants to merge 1 commit into
Closed
deps(deps-dev): bump @vitest/coverage-v8 from 2.1.9 to 4.1.10#79dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) from 2.1.9 to 4.1.10. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.10/packages/coverage-v8) --- updated-dependencies: - dependency-name: "@vitest/coverage-v8" dependency-version: 4.1.10 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
scttfrdmn
added a commit
that referenced
this pull request
Aug 16, 2026
vitest and @vitest/coverage-v8 must stay on the same major version (coverage-v8 peer-depends on the exact vitest version). Bumping vitest alone to 4.1.10 (this PR) while coverage-v8 stayed on ^2.1.9 caused an ERESOLVE conflict in CI. Bump both together here; PR #79 (the separate coverage-v8-only bump) is superseded by this change. Verified locally: typecheck, vitest run (594/594), test:cov, build, build:lib, check:exports, check:imports all pass.
scttfrdmn
added a commit
that referenced
this pull request
Aug 16, 2026
* deps(deps-dev): bump vitest from 2.1.9 to 4.1.10 Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 2.1.9 to 4.1.10. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.10/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 4.1.10 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> * deps(deps-dev): bump @vitest/coverage-v8 to 4.1.10 alongside vitest vitest and @vitest/coverage-v8 must stay on the same major version (coverage-v8 peer-depends on the exact vitest version). Bumping vitest alone to 4.1.10 (this PR) while coverage-v8 stayed on ^2.1.9 caused an ERESOLVE conflict in CI. Bump both together here; PR #79 (the separate coverage-v8-only bump) is superseded by this change. Verified locally: typecheck, vitest run (594/594), test:cov, build, build:lib, check:exports, check:imports all pass. --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: scttfrdmn <3011922+scttfrdmn@users.noreply.github.com>
Contributor
Author
|
Looks like @vitest/coverage-v8 is up-to-date now, so this is no longer needed. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/vitest/coverage-v8-4.1.10
branch
August 16, 2026 21:49
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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/coverage-v8 from 2.1.9 to 4.1.10.
Release notes
Sourced from @vitest/coverage-v8's releases.
... (truncated)
Commits
db616d2chore: release v4.1.10 (#10718)a7a61e7chore: release v4.1.9 (#10598)e61f2ddchore: release v4.1.8e4067b3fix(browser): disable clientcdpAPI whenallowWrite/allowExec: false[ba...a09d472chore: release v4.1.7a8fd24cchore: release v4.1.6e399846chore: release v4.1.5ac04bacchore: release v4.1.42dc0d62chore: release v4.1.3fc6f482chore: release v4.1.2Maintainer changes
This version was pushed to npm by GitHub Actions, 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 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)