chore(deps-dev): bump vitest from 4.1.8 to 4.1.9

[dependabot]

Bumps vitest from 4.1.8 to 4.1.9.

Release notes

Sourced from vitest's releases.

v4.1.9

🐞 Bug Fixes

• Fix importOriginal with optimizer and query import [backport to v4] - by Hiroshi Ogawa, David Harris, Codexand Vladimir in vitest-dev/vitest#10546 (a5180)
• browser:
  • Wait for orchestrator readiness before resolving browser sessions [backport to v4] - by Vladimir and Séamus O'Connor in vitest-dev/vitest#10555 (7fb29)
  • Wait for iframe tester readiness before preparing [backport to v4] - by Vladimir and Séamus O'Connor in vitest-dev/vitest#10497 and vitest-dev/vitest#10556 (fbc62)
• mocker:
  • Hoist vi.mock() for vite-plus/test imports [backport to v4] - by Hiroshi Ogawa, LongYinan, Claude Opus 4.8 and Vladimir in vitest-dev/vitest#10548 (2c955)
• pool:
  • Prevent test run hang on worker crash [backport to v4] - by Ari Perkkiö and Jattioui Ismail in vitest-dev/vitest#10543 and vitest-dev/vitest#10564 (934b0)

View changes on GitHub

Commits

• a7a61e7 chore: release v4.1.9 (#10598)
• 934b0f5 fix(pool): prevent test run hang on worker crash (#10543) [backport to v4] (#...
• 7fb2965 fix(browser): wait for orchestrator readiness before resolving browser sessio...
• a518019 fix: fix importOriginal with optimizer and query import [backport to v4] (#...
• See full diff in compare view

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: javascript. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[greptile-apps]

Greptile Summary

This PR bumps vitest from 4.1.8 to 4.1.9 (patch), picking up bug fixes for importOriginal with the optimizer, browser session readiness, vi.mock() hoisting, and a worker-crash hang in the pool. However, @vitest/coverage-v8 was not bumped alongside it, leaving a peer dependency version mismatch.

• vitest is updated to 4.1.9 in package.json and the lock file, along with all its first-party sub-packages (@vitest/expect, @vitest/runner, @vitest/spy, @vitest/snapshot, @vitest/mocker, @vitest/utils, @vitest/pretty-format).
• @vitest/coverage-v8 remains at 4.1.8 (specifier ^4.1.8 in package.json), while [email protected]'s peer dependency declaration now requires @vitest/[email protected]. This causes a split in @vitest/utils versions (4.1.8 used by coverage-v8 vs 4.1.9 used by vitest), and pnpm test:coverage may emit peer dependency warnings or behave incorrectly.

Confidence Score: 4/5

Safe to merge for basic test runs, but coverage reporting may break or emit peer dependency warnings due to the version split between vitest and @vitest/coverage-v8.

All vitest core sub-packages are consistently updated to 4.1.9, but @vitest/coverage-v8 was left at 4.1.8 while vitest 4.1.9 now declares it as a peer at 4.1.9. This pulls in two different versions of @vitest/utils into the graph and contradicts vitest's own peer dependency declaration. The pnpm test:coverage workflow is the affected path.

package.json — the @vitest/coverage-v8 specifier should be bumped from ^4.1.8 to ^4.1.9 to match the updated vitest peer dependency requirement.

Important Files Changed

Filename	Overview
package.json	vitest bumped to ^4.1.9, but @vitest/coverage-v8 stays at ^4.1.8, creating a peer dependency version mismatch
pnpm-lock.yaml	Lock file correctly reflects [email protected] and its sub-packages, but @vitest/coverage-v8 resolves to 4.1.8 while vitest 4.1.9 declares it as a peer requiring 4.1.9

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[vitest 4.1.9] -->|uses| B[vitest-expect 4.1.9]
    A -->|uses| C[vitest-runner 4.1.9]
    A -->|uses| D[vitest-utils 4.1.9]
    A -->|uses| E[vitest-mocker 4.1.9]
    A -->|peer dep expects 4.1.9| G[coverage-v8 4.1.8 MISMATCH]
    G -->|uses| H[vitest-utils 4.1.8]
    style G fill:#ffcccc,stroke:#ff0000
    style H fill:#ffcccc,stroke:#ff0000

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[vitest 4.1.9] -->|uses| B[vitest-expect 4.1.9]
    A -->|uses| C[vitest-runner 4.1.9]
    A -->|uses| D[vitest-utils 4.1.9]
    A -->|uses| E[vitest-mocker 4.1.9]
    A -->|peer dep expects 4.1.9| G[coverage-v8 4.1.8 MISMATCH]
    G -->|uses| H[vitest-utils 4.1.8]
    style G fill:#ffcccc,stroke:#ff0000
    style H fill:#ffcccc,stroke:#ff0000

Loading

Comments Outside Diff (1)

1. package.json, line 50 (link)

   @vitest/coverage-v8 is still pinned to ^4.1.8 while vitest was bumped to ^4.1.9. The [email protected] package declares @vitest/coverage-v8: 4.1.9 as a peer dependency, so keeping coverage-v8 at 4.1.8 causes a peer dependency mismatch. The lock file confirms that @vitest/[email protected] is being used alongside [email protected], pulling in @vitest/[email protected] for coverage while the rest of the stack uses @vitest/[email protected]. Running test:coverage may produce warnings or unexpected behavior due to this split.

   

_{Reviews (1): Last reviewed commit: "chore(deps-dev): bump vitest from 4.1.8 ..." | Re-trigger Greptile}