chore(deps): bump the testing group with 2 updates#298
chore(deps): bump the testing group with 2 updates#298dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps the testing 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 4.0.18 to 4.1.0 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.0/packages/coverage-v8) Updates `vitest` from 4.0.18 to 4.1.0 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.0/packages/vitest) --- updated-dependencies: - dependency-name: "@vitest/coverage-v8" dependency-version: 4.1.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: testing - dependency-name: vitest dependency-version: 4.1.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: testing ... 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 |
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
✔️ Bundle Size Analysis
Bundle breakdown |
There was a problem hiding this comment.
LGTM — straightforward Dependabot lockfile update for vitest 4.0.18 → 4.1.0.
Extended reasoning...
Overview
This PR is an automated Dependabot bump updating vitest and @vitest/coverage-v8 from 4.0.18 to 4.1.0. The only file changed is pnpm-lock.yaml, reflecting the new resolved versions and their transitive dependencies (esbuild 0.27.4, rollup 4.59.0, postcss 8.5.8, etc.).
Security risks
No security risks identified. This is a minor version bump of well-known testing dependencies. No application source code, configuration, or build pipeline files are modified — only the lockfile.
Level of scrutiny
Minimal scrutiny is appropriate. This is a lockfile-only change generated by Dependabot for dev dependencies (testing tools). It does not affect production code, runtime behavior, or CI/CD configuration.
Other factors
No bugs were found by the automated bug hunting system. No outstanding reviewer comments exist. The specifiers in package.json use ^4.0.18 ranges, so 4.1.0 is within the expected semver range. The PR is labeled dependencies and follows the established pattern of prior Dependabot PRs in this repository.
Bumps the testing group with 2 updates: @vitest/coverage-v8 and vitest.
Updates
@vitest/coverage-v8from 4.0.18 to 4.1.0Release notes
Sourced from
@vitest/coverage-v8's releases.... (truncated)
Commits
4150b91chore: release v4.1.00c2c013chore: release v4.1.0-beta.6689a22afix(browser): types ofgetCDPSessionandcdp()(#9716)94eb73bchore(deps): update eslint packages (#9615)8c96bb0refator: update links to npmx (#9783)aaf7758chore: standardize packages README (#9776)57cbe39chore(deps): updateast-v8-to-istanbulto v1 (#9755)79672d7chore: release v4.1.0-beta.51d9e3b3chore: release v4.1.0-beta.44ff8c6fchore(build): raise build target to the minimum supported, don't bundle utils...Updates
vitestfrom 4.0.18 to 4.1.0Release notes
Sourced from vitest's releases.
... (truncated)
Commits
4150b91chore: release v4.1.01de0aa2fix: correctly identify concurrent test during static analysis (#9846)c3cac1cfix: use isAgent check, not just TTY, for watch mode (#9841)eab68bachore(deps): update all non-major dependencies (#9824)031f02afix: allow catch/finally for async assertion (#9827)3e9e096feat(reporters): addagentreporter to reduce ai agent token usage (#9779)0c2c013chore: release v4.1.0-beta.68181e06fix:hideSkippedTestsshould not hidetest.todo(fix #9562) (#9781)a8216b0fix: manual and redirect mock shouldn'tloadortransformoriginal module...689a22afix(browser): types ofgetCDPSessionandcdp()(#9716)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