Repository navigation
chore(deps): hold vitest below 5 and group vitest packages in Dependabot - #144
Merged
Merged
Conversation
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.
This was referenced Oct 21, 2026
felipesauer
added a commit
that referenced
this pull request
Oct 21, 2026
) Adds the three decisions settled while clearing the Dependabot queue, and their acceptance, to the signed record under .mnema/. Only the tail files changed, and no key material is involved. - ADR-1 runs the commitlint PR-title check only for human-authored PRs (#141). - ADR-2 holds mermaid at 11 and ignores semver-major mermaid updates in Dependabot (#141). - ADR-3 holds vitest below 5 until the Stryker vitest-runner is fixed, with vitest and @vitest/* grouped so they arrive together (#144).
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.
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.
exact vitest version as a peer, so separate PRs can never install or pass, as with chore(deps): bump @vitest/coverage-v8 from 4.1.11 to 5.0.3 #134 and chore(deps): bump vitest from 4.1.11 to 5.0.3 #136.
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.