chore(deps-dev): bump @vitest/coverage-v8 from 4.1.8 to 4.1.9

[dependabot]

Bumps @vitest/coverage-v8 from 4.1.8 to 4.1.9.

Release notes

Sourced from @​vitest/coverage-v8'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)
• 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 is a routine Dependabot patch bump of the dev dependency @vitest/coverage-v8 from 4.1.8 to 4.1.9. The lock file is updated accordingly with new integrity hashes and a handful of transitive dependency bumps.

• package.json updates the version specifier to ^4.1.9; the lock file resolves @vitest/[email protected] alongside its updated transitive deps (@vitest/utils, @vitest/pretty-format, ast-v8-to-istanbul, obug, semver, @types/estree)
• vitest itself stays at 4.1.8, which means @vitest/[email protected]'s declared peer requirement of vitest: 4.1.9 is technically unmet — pnpm still resolved the pair (shown in the lock file snapshot key 4.1.9([email protected])), so no install failure occurs, but upgrading vitest to 4.1.9 as well would keep the ecosystem in sync

Confidence Score: 5/5

Safe to merge; this is a dev-only patch release for the coverage reporter with no changes to production code.

The bump is limited to a test-coverage dev dependency and its transitive chain. All changed packages are patch-level releases. The only minor wrinkle is that vitest stays at 4.1.8 while @vitest/[email protected] now declares vitest: 4.1.9 as a peer — pnpm resolved them together without error, and the two packages are part of the same release monorepo so patch-level skew is typically benign. No production code or runtime dependencies are affected.

No files require special attention; both changes are mechanical lock-file updates.

Important Files Changed

Filename	Overview
package.json	Dev-dependency version specifier bumped from ^4.1.8 to ^4.1.9 for @vitest/coverage-v8; no other changes.
pnpm-lock.yaml	Lock file updated to resolve @vitest/[email protected] with new integrity hashes; transitive deps (@vitest/utils, ast-v8-to-istanbul, obug, semver, @types/estree) also bumped to their latest patch versions. vitest itself remains at 4.1.8, creating a minor peer-version skew.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["@vitest/[email protected]\n(bumped)"] --> B["@vitest/[email protected]\n(transitive bump)"]
    A --> C["[email protected]\n(transitive bump)"]
    A --> D["[email protected]\n(transitive bump)"]
    B --> E["@vitest/[email protected]\n(transitive bump)"]
    C --> F["@types/[email protected]\n(transitive bump)"]
    G["[email protected]"] --> H["[email protected]\n(transitive bump)"]
    I["[email protected]\n(unchanged)"] -. "peer dep expects 4.1.9" .-> A

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/[email protected]\n(bumped)"] --> B["@vitest/[email protected]\n(transitive bump)"]
    A --> C["[email protected]\n(transitive bump)"]
    A --> D["[email protected]\n(transitive bump)"]
    B --> E["@vitest/[email protected]\n(transitive bump)"]
    C --> F["@types/[email protected]\n(transitive bump)"]
    G["[email protected]"] --> H["[email protected]\n(transitive bump)"]
    I["[email protected]\n(unchanged)"] -. "peer dep expects 4.1.9" .-> A

Loading

_{Reviews (1): Last reviewed commit: "chore(deps-dev): bump @vitest/coverage-v..." | Re-trigger Greptile}