Skip to content

chore(deps-dev): bump vitest from 3.2.7 to 4.1.11 - #54

Merged
LRainner merged 1 commit into
masterfrom
dependabot/npm_and_yarn/vitest-4.1.11
Sep 11, 2026
Merged

LRainner merged 1 commit into
masterfrom
dependabot/npm_and_yarn/vitest-4.1.11

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 11, 2026

Copy link
Copy Markdown
Contributor

Bumps vitest from 3.2.7 to 4.1.11.

Release notes

Sourced from vitest's releases.

v4.1.11

   🐞 Bug Fixes

    View changes on GitHub

v4.1.10

   🐞 Bug Fixes

    View changes on GitHub

v4.1.9

🐞 Bug Fixes

View changes on GitHub

v4.1.8

   🐞 Bug Fixes

    View changes on GitHub

v4.1.7

   🐞 Bug Fixes

    View changes on GitHub

... (truncated)

Commits
  • 9bd8d46 chore: release v4.1.11 (#10995)
  • 9851dbc fix(browser): trigger playwright/chromium gc on lower disk availability [back...
  • db616d2 chore: release v4.1.10 (#10718)
  • bae52b5 fix(vm): fix external module resolve error with deps optimizer query for enco...
  • a7a61e7 chore: release v4.1.9 (#10598)
  • 934b0f5 fix(pool): prevent test run hang on worker crash (#10543) [backport to v4] (#...
  • 7fb2965 fix(browser): wait for orchestrator readiness before resolving browser sessio...
  • a518019 fix: fix importOriginal with optimizer and query import [backport to v4] (#...
  • e61f2dd chore: release v4.1.8
  • e4067b3 fix(browser): disable client cdp API when allowWrite/allowExec: false [ba...
  • Additional commits viewable in compare view

Dependabot compatibility score

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)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 3.2.7 to 4.1.11.
- [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.11/packages/vitest)

---
updated-dependencies:
- dependency-name: vitest
  dependency-version: 4.1.11
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 11, 2026
@monkeyscan

monkeyscan Bot commented Sep 11, 2026

Copy link
Copy Markdown

PR Title: chore(deps-dev): bump vitest from 3.2.7 to 4.1.11

Commit: 7c3a39b

本 PR 仅做依赖升级:package.json 将 devDependency vitest^3.2.0 提升到 ^4.1.11(跨主版本 3→4),并同步重新生成 package-lock.json(+135/-231)。\n\n核对结论:lock 文件内部自洽——根 packages[\"\"] 的 devDependencies 已更新为 ^4.1.11node_modules/vitest 为 4.1.11,std-env 实际解析到 4.2.0(满足 ^4.0.0-rc.1),vite 7.3.6 满足 vitest 4 的 vite: ^6||^7||^8 必需 peer;vitest 4 的 engines^20.0.0 || ^22.0.0 || >=24.0.0,与 README 声明的 Node 20.19+ 要求一致,故无 Node 版本兼容性回归。现有 vitest.config.ts(defineConfig + root + test.include)与 vite.config.ts 均为最小配置,主版本升级未引入显式配置不兼容。\n\n主要风险:这是测试运行器的破坏性主版本升级,但 PR 未附带任何测试/配置调整或验证证据。vitest 4 存在快照格式、mock/spy 语义及被移除 API 等 breaking change,可能让既有测试静默失败,建议合并前以 npm ci && npm test 全量验证(含快照)后再合并。此外 lock 中 vitest 传递依赖出现 std-env@^4.0.0-rc.1 预发布范围,虽已解析到稳定 4.2.0,仍属可留意的供应链/稳定性细节。

Prompt To Fix All With AI
This is a comment left during a code review.
Repository: https://github.com/LRainner/AgentCat
Path: package.json
Line: 28

Comment:
vitest 跨主版本升级 3→4 缺少配套的配置/测试验证,存在测试套件回归风险

本改动把 devDependency `vitest` 从 `^3.2.0` 直接升级到 `^4.1.11`,属于破坏性主版本升级,但 diff 中除 package.json 一行与自动生成的 package-lock.json 外,没有任何测试代码或 vitest 配置的相应调整。经核对:vitest.config.ts 仍为 `defineConfig` + `root` + `test.include` 的最小配置,`vite.config.ts` 的 `root: "src"` 也未变;仓库中 `npm test` 使用 `vitest run` 收集 `src/**/*.test.ts` 与 `plugins/**/*.test.js`。vitest 4 相对 3 存在多处 breaking change(如移除 Node 18 支持、快照序列化格式变更、mock/spy 语义与部分被移除的 API/选项),这些变化会在不改动测试的情况下改变断言与快照行为,可能让既有测试静默失败或产生误报。当前 PR 未提供任何运行 `npm ci && npm test` 通过或快照已更新的证据,因此无法确认测试套件在 v4 下仍然成立。
---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

@coderabbitai

coderabbitai Bot commented Sep 11, 2026

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: db99c055-afe2-4840-a6d7-5b5a24f496ed

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

Comment thread package.json
"typescript": "^5.8.0",
"vite": "^7.0.0",
"vitest": "^3.2.0"
"vitest": "^4.1.11"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

vitest 跨主版本升级 3→4 缺少配套的配置/测试验证,存在测试套件回归风险

本改动把 devDependency vitest^3.2.0 直接升级到 ^4.1.11,属于破坏性主版本升级,但 diff 中除 package.json 一行与自动生成的 package-lock.json 外,没有任何测试代码或 vitest 配置的相应调整。经核对:vitest.config.ts 仍为 defineConfig + root + test.include 的最小配置,vite.config.tsroot: "src" 也未变;仓库中 npm test 使用 vitest run 收集 src/**/*.test.tsplugins/**/*.test.js。vitest 4 相对 3 存在多处 breaking change(如移除 Node 18 支持、快照序列化格式变更、mock/spy 语义与部分被移除的 API/选项),这些变化会在不改动测试的情况下改变断言与快照行为,可能让既有测试静默失败或产生误报。当前 PR 未提供任何运行 npm ci && npm test 通过或快照已更新的证据,因此无法确认测试套件在 v4 下仍然成立。

Problem code:

"vitest": "^4.1.11"

Recommendation:
在合并前用 npm ci 后运行 npm test 验证全部用例通过(含快照用例),若存在快照不匹配或使用已移除 API 的测试,需在本 PR 内一并更新;同时确认 CI/开发环境 Node 版本满足 vitest 4 的 engines(^20.0.0 || ^22.0.0 || >=24.0.0,已与 README 的 Node 20.19+ 要求一致)。

Prompt To Fix All With AI
This is a comment left during a code review.
Repository: https://github.com/LRainner/AgentCat
Path: package.json
Line: 28

Comment:
vitest 跨主版本升级 3→4 缺少配套的配置/测试验证,存在测试套件回归风险

本改动把 devDependency `vitest` 从 `^3.2.0` 直接升级到 `^4.1.11`,属于破坏性主版本升级,但 diff 中除 package.json 一行与自动生成的 package-lock.json 外,没有任何测试代码或 vitest 配置的相应调整。经核对:vitest.config.ts 仍为 `defineConfig` + `root` + `test.include` 的最小配置,`vite.config.ts` 的 `root: "src"` 也未变;仓库中 `npm test` 使用 `vitest run` 收集 `src/**/*.test.ts` 与 `plugins/**/*.test.js`。vitest 4 相对 3 存在多处 breaking change(如移除 Node 18 支持、快照序列化格式变更、mock/spy 语义与部分被移除的 API/选项),这些变化会在不改动测试的情况下改变断言与快照行为,可能让既有测试静默失败或产生误报。当前 PR 未提供任何运行 `npm ci && npm test` 通过或快照已更新的证据,因此无法确认测试套件在 v4 下仍然成立。
---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Fix with MonkeyCode
Fix with Claude
Fix with Codex

@LRainner
LRainner merged commit 0a993dd into master Sep 11, 2026
7 checks passed
@LRainner
LRainner deleted the dependabot/npm_and_yarn/vitest-4.1.11 branch September 11, 2026 08:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant