fix: update @vitest/coverage-v8 version to use caret range

[phillipc]

@vitest/coverage-v8 was pinned to an exact version (4.1.7) while all other @vitest/* packages in devDependencies use a caret range (^4.1.7). This inconsistency caused version mismatches when Bun resolved the lockfile.

Change: "@vitest/coverage-v8": "4.1.7" → "@vitest/coverage-v8": "^4.1.7"

Summary by CodeRabbit

• Chores
  • Updated development dependency version constraints.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: cc052be2-e58d-4ed2-8521-fb4eb913c483

📥 Commits

Reviewing files that changed from the base of the PR and between c094817 and 67f5668.

⛔ Files ignored due to path filters (1)

• bun.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• package.json

---

📝 Walkthrough

Walkthrough

The @vitest/coverage-v8 dev dependency version specifier is updated from a pinned version 4.1.7 to a caret range ^4.1.7, allowing patch and minor version updates during installation.

Changes

Dependency Configuration

Layer / File(s)	Summary
Vitest coverage dependency range update package.json	The @vitest/coverage-v8 dev dependency version specifier is changed from exact version 4.1.7 to caret range ^4.1.7.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• knockout/tko#364: Both PRs modify package.json's devDependencies for @vitest/coverage-v8, adjusting its version or range.

Suggested reviewers

• brianmhunt

Poem

🐰 A single line, a caret small,
Now patches flow through one and all,
The coverage doth adapt with grace,
No versions pinned down to this place! 📦✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: updating @vitest/coverage-v8 from a fixed version to a caret range, which directly addresses the version inconsistency issue.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/v8_version_patching

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}