chore(deps-dev): bump vitest from 2.1.9 to 4.0.18#7
Closed
dependabot[bot] wants to merge 1 commit intomasterfrom
Closed
chore(deps-dev): bump vitest from 2.1.9 to 4.0.18#7dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot[bot] wants to merge 1 commit intomasterfrom
Conversation
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) 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/vitest) --- updated-dependencies: - dependency-name: vitest 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}
| "tsx": "^4.19.2", | ||
| "typescript": "^5.7.2", | ||
| "vitest": "^2.1.8", | ||
| "vitest": "^4.0.18", |
There was a problem hiding this comment.
Bug: The vitest package is updated to v4, but the @vitest/coverage-v8 package is not. This version mismatch will cause a peer dependency conflict and break the CI build.
Severity: HIGH
Suggested Fix
To resolve the peer dependency conflict, update the @vitest/coverage-v8 package to a version compatible with vitest v4. Change @vitest/coverage-v8 from ^2.1.8 to ^4.0.18 in package.json.
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#L66
Potential issue: The pull request updates `vitest` to version `^4.0.18` but leaves
`@vitest/coverage-v8` at `^2.1.8`. This creates a peer dependency conflict, as the older
coverage package requires a `vitest` version compatible with v2. After this change is
merged, the `bun install` command will result in incompatible package versions.
Consequently, the `test:coverage` script, which runs `vitest run --coverage` in the CI
pipeline, will fail at runtime. Vitest enforces version matching between its core and
plugin packages across major versions, so invoking the v2 coverage provider with the v4
core will cause the CI build to fail.
Did we get this right? 👍 / 👎 to inform future reviews.
Author
|
Superseded by #15. |
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 from 2.1.9 to 4.0.18.
Release notes
Sourced from vitest's releases.
... (truncated)
Commits
4d3e3c6chore: release v4.0.18ea837defeat(experimental): addonModuleRunnerhook toworker.init(#9286)e057281fix: usemeta.urlincreateRequire(#9441)dd54e94chore: release v4.0.1759f92d4fix(fsModuleCache): add importers alongside importedModules (#9423)751364efix(fsModuleCache): don't store importers in cache (#9422)4b67fc2fix: typo in browser.provider error (#9394)40841fffix: handle null options inaddEventHandler#9371 (#9372)200dadbfix(pool): handle worker start failures gracefully (#9337)1500654fix(browser): supportfileParallelismon an instance (#9328)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), 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 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)