chore(deps): bump @vitest/coverage-v8 from 4.1.5 to 4.1.7#144
Conversation
Bumps [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) from 4.1.5 to 4.1.7. - [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/v4.1.7/packages/coverage-v8) --- updated-dependencies: - dependency-name: "@vitest/coverage-v8" dependency-version: 4.1.7 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
📝 WalkthroughWalkthroughThe ChangesVitest Coverage Dependency Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@package.json`:
- Line 82: Dependency "`@vitest/coverage-v8`" is specified with a caret range
(^4.1.7); change it to the exact version "4.1.7" in package.json and update the
lockfile (run npm install / yarn install) so the lockfile reflects the pinned
version; ensure only the dependency string for "`@vitest/coverage-v8`" is changed
and commit both package.json and the updated lockfile.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: 5b0ef429-e8c0-4b03-809d-7ad3bceb0bd6
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (1)
package.json
Constraint: CodeRabbit requested exact @vitest/coverage-v8 version on PR #144.\nRejected: Leave caret range | PR remains review-blocked by the dependency policy comment.\nConfidence: high\nScope-risk: narrow\nDirective: Keep this PR scoped to the coverage-v8 pin; do not fold the sibling vitest bump into this branch.\nTested: corepack pnpm install --lockfile-only; corepack pnpm install; corepack pnpm -r build; git diff --check\nNot-tested: corepack pnpm test still fails local tarball-smoke tests for missing dist/index.js under Node v26.0.0, unrelated to this dependency specifier change.
Constraint: Main advanced with sibling Dependabot merges while PR #144 was rerunning after the CodeRabbit pin fix.\nRejected: Force-push a rebase | A normal merge commit preserves the active PR branch history without rewriting Dependabot's branch.\nConfidence: high\nScope-risk: narrow\nDirective: Keep this branch limited to @vitest/coverage-v8 pinning plus merge-conflict resolution from current main.\nTested: corepack pnpm install --lockfile-only\nNot-tested: Full tests not rerun after this merge resolution; previous local full test was blocked by unrelated tarball-smoke failures under Node v26.0.0.
Bumps @vitest/coverage-v8 from 4.1.5 to 4.1.7.
Release notes
Sourced from @vitest/coverage-v8's releases.
Commits
a09d472chore: release v4.1.7a8fd24cchore: release v4.1.6Dependabot 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)Need help on this PR? Tag
@codesmithwith what you need. Autofix is disabled.Summary by CodeRabbit