Repository navigation
chore(deps): bump vitest from 4.1.11 to 5.0.3 - #136
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 4.1.11 to 5.0.3. - [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/v5.0.3/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 5.0.3 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
|
Closing: vitest 5 cannot be adopted yet.
This PR also could not pass on its own: Semver-major updates of |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
…bot (#144) vitest 5 cannot be adopted yet because the Stryker vitest-runner (10.0.0, the latest release) breaks on it. Its per-test name filter matches nothing under vitest 5, so every covered mutant survives. The mutation score falls from about 85% to 0.88% on a local run, while the unit tests and v8 coverage stay green at 100%. Tracked upstream as stryker-mutator/stryker-js#6210. - Ignore semver-major updates of vitest and @vitest/* until Stryker ships a fix. - Group vitest and @vitest/* so minor and patch bumps arrive in one PR. coverage-v8 requires the exact vitest version as a peer, so separate PRs can never install or pass, as with #134 and #136. - Keep them out of the npm group with exclude-patterns, so grouping does not depend on order. Revisit once a @stryker-mutator/vitest-runner release fixes the filter. Then drop the two ignore entries and bump vitest and @vitest/coverage-v8 together.
1 participant
Bumps vitest from 4.1.11 to 5.0.3.
Release notes
Sourced from vitest's releases.
... (truncated)
Commits
33cadeachore: release v5.0.3 (#11409)346d389fix(vm): don't reuse scripts across vite environments (#11395)f6c9a49fix(deps): pinwhy-is-node-runningto3.2.1to avoid users running into `...062c75dchore: fix standalone docs build, update exports maps (#11394)caf2887fix(vm): do not optimize deps from index.html (fix #11329) (#11360)50312ebfix(pool): preserve unique pool ids whengroupOrderis set (#11392)7c36748fix(browser): ignore page crash while cancelling (#11386)92ba7fcfix: scope cache key generators to projects (fix #11281) (#11301)38f9885fix(cache): revalidate imports of cached modules (#11381)b24585ffix: don't retry whentest.failsexpectedly failed (#11219)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)