Repository navigation
build(deps-dev): bump the development group with 2 updates - #112
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps the development group with 2 updates: [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) and [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest). Updates `@vitest/coverage-v8` from 5.0.4 to 5.0.5 - [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/v5.0.5/packages/coverage-v8) Updates `vitest` from 5.0.4 to 5.0.5 - [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/v5.0.5/packages/vitest) --- updated-dependencies: - dependency-name: "@vitest/coverage-v8" dependency-version: 5.0.5 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: development - dependency-name: vitest dependency-version: 5.0.5 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: development ... Signed-off-by: dependabot[bot] <support@github.com>
|
🦞👀 Pull request received. I will update this pull request when review starts. ClawSweeper review completeClawSweeper finished reviewing this revision. The review result is being finalized. |
|
Codex review: needs maintainer review before merge. What this changesThis PR updates the locked Vitest and V8 coverage packages from 5.0.4 to 5.0.5. Example: A contributor installs dependencies with pnpm install --frozen-lockfile.
Review scores
ProductKind: Maintenance · Worth it: Yes · Fix scope: Complete Merge readiness✅ Ready for maintainer review Keep this PR open: main still uses Vitest 5.0.4, and this focused patch update has passing checks with no concrete introduced defect found. Priority: P3 Before mergeNone. FindingsNone. Agent review detailsHow this fits togetherThe lockfile selects development tools used by the repository's test and coverage scripts; these packages are separate from the published terminal runtime dependencies. flowchart LR
A[Package dependency ranges] --> B[pnpm lockfile]
B --> C[Frozen dependency installation]
C --> D[Vitest runner]
D --> E[Terminal library tests]
D --> F[V8 coverage reports]
Technical reviewBest possible solution: Retain the focused lockfile update with Vitest and its coverage provider aligned. Do we have a high-confidence way to reproduce the issue? This is dependency maintenance rather than a reported libterminal bug, so a failing reproduction is not applicable. Is this the best way to solve the issue? The lockfile-only update is appropriately narrow, satisfies the existing manifest ranges, and preserves the established matching-provider contract. AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning medium; reviewed against 4961b34d8dcf. Provenance checked
TestingProof path: unit tests only. SecurityNone. EvidenceWhat I checked:
LabelsLabel changes:
Label justifications:
Rating scale6/6 🦀 challenger crab · 5/6 🦞 diamond lobster · 4/6 🐚 platinum hermit · 3/6 🦐 gold shrimp · 2/6 🦪 silver shellfish · 1/6 🧂 unranked krab. Overall follows the weaker of proof and patch quality; ✨ marks media proof (a screenshot, video, or linked artifact) that directly shows the changed behavior. WorkflowClawSweeper edits this one comment on every review. Comment Reviewed October 19, 2026, 1:29 PM ET / 17:29 UTC. |
Update Vitest and its matching V8 coverage provider to 5.0.5, and the paired CodeQL actions to 4.39.0. Consolidate Dependabot #112 and #113 with an Unreleased note, preserving runtime floors and the two-day cooldown. Validation: frozen installation, pnpm check, coverage (140 tests), and nine Chromium browser tests passed. Independent P0–P3 autoreview is scoped-clean. Exact-head CI 39485321435 and CodeQL 39485321881 passed across supported Node.js versions and platforms. Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
Included in #114, merged as c5e11c3. Vitest and the V8 coverage provider are now both 5.0.5. Frozen install, package checks, all 140 unit tests, coverage, nine browser tests, and the exact-head cross-platform CI passed. Dependabot credit is preserved in the changelog and squash commit. Closing this superseded update. |
|
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests. To ignore these dependencies, configure ignore rules in dependabot.yml |
Bumps the development group with 2 updates: @vitest/coverage-v8 and vitest.
Updates
@vitest/coverage-v8from 5.0.4 to 5.0.5Release notes
Sourced from @vitest/coverage-v8's releases.
Commits
7a825dbchore: release v5.0.5 (#11609)Updates
vitestfrom 5.0.4 to 5.0.5Release notes
Sourced from vitest's releases.
Commits
7a825dbchore: release v5.0.5 (#11609)6621a72fix: abort all running tests on cancel (#11606)e9c3d72fix: release mocks of finished test files (#11607)8dd67c2fix(browser): run global setup once with instances (#11596)6c5a447fix: run hook cleanups when a later hook fails (#11605)9697b38fix: keep the import frame in native loader errors (#11599)6498b66fix(browser): wait 30s for the browser to close (#11601)f161e6dfix(browser): drop late connections of closed sessions (#11600)fe86a64fix: skip builtin loading in async leak detector (#11598)6ae8e89fix(reporter): end reason'failed'on worker crash (#11568)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 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 <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions