chore(deps-dev): bump @vitest/coverage-v8 from 2.1.9 to 4.0.18#4
Closed
dependabot[bot] wants to merge 1 commit intomasterfrom
Closed
chore(deps-dev): bump @vitest/coverage-v8 from 2.1.9 to 4.0.18#4dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot[bot] wants to merge 1 commit intomasterfrom
Conversation
Bumps [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) from 2.1.9 to 4.0.18. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.0.18/packages/coverage-v8) --- updated-dependencies: - dependency-name: "@vitest/coverage-v8" dependency-version: 4.0.18 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
| "@types/node": "^22.10.0", | ||
| "@types/ws": "^8.18.1", | ||
| "@vitest/coverage-v8": "^2.1.8", | ||
| "@vitest/coverage-v8": "^4.0.18", |
There was a problem hiding this comment.
Bug: The PR updates @vitest/coverage-v8 to a new major version (v4) but leaves vitest at v2. These packages must share the same major version to be compatible.
Severity: CRITICAL
Suggested Fix
To resolve the incompatibility, update the vitest package in package.json to a version compatible with @vitest/coverage-v8 v4, such as ^4.0.18. Both packages should share the same major version. After updating package.json, run bun install to update the bun.lock file accordingly.
Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.
Location: package.json#L62
Potential issue: The pull request upgrades `@vitest/coverage-v8` to version `^4.0.18`
while `vitest` remains at `^2.1.8`. Vitest and its related packages, like
`@vitest/coverage-v8`, are tightly coupled and require matching major versions for
compatibility. Attempting to run tests with coverage via `vitest run --coverage` will
cause a failure. The v2 `vitest` runner will be unable to initialize the v4 coverage
plugin due to breaking API changes between the major versions, which will break the
CI/CD pipeline's `coverage` job.
Did we get this right? 👍 / 👎 to inform future reviews.
Author
|
Superseded by #16. |
dependabot
bot
deleted the
dependabot/npm_and_yarn/vitest/coverage-v8-4.0.18
branch
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.0.18.
Release notes
Sourced from
@vitest/coverage-v8's releases.... (truncated)
Commits
4d3e3c6chore: release v4.0.18dd54e94chore: release v4.0.1729ee7f5chore(deps): updateast-v8-to-istanbul(#9418)b094053fix(coverage): remove unnecessaryistanbul-lib-source-mapsusage (#9344)b46d744chore: release v4.0.16eb1abf0chore: release v4.0.159ca74cfchore: release v4.0.14acc5152perf: replacedebugwithobug(#9057)73b54cechore: release v4.0.135aa84d5chore: release v4.0.12Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~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)