Skip to content

chore(deps-dev): bump the development-tooling group across 1 directory with 13 updates - #200

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/development-tooling-5c71a9bceb
Open

chore(deps-dev): bump the development-tooling group across 1 directory with 13 updates#200
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/development-tooling-5c71a9bceb

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 27, 2026

Copy link
Copy Markdown

Bumps the development-tooling group with 13 updates in the / directory:

Package From To
@biomejs/biome 2.5.8 2.5.10
@types/node 22.20.1 26.2.0
@vitest/coverage-v8 3.2.7 4.1.11
tsdown 0.21.4 0.22.14
turbo 2.10.10 2.10.11
typescript 5.9.3 7.0.2
vitest 3.2.7 4.1.11
commander 13.1.0 15.0.0
@types/react-dom 19.2.4 19.2.5
@vitejs/plugin-react 4.7.0 6.1.0
jsdom 26.1.0 30.0.1
vite 7.3.6 8.2.2
@testcontainers/postgresql 11.14.0 12.1.0

Updates @biomejs/biome from 2.5.8 to 2.5.10

Release notes

Sourced from @​biomejs/biome's releases.

Biome CLI v2.5.10

2.5.10

Patch Changes

  • #11403 8f7786f Thanks @​Princesseuh! - Fixed Astro rejecting JavaScript comments between attributes.

    <div /* block comment */ class="something"></div>
<Component /* c */ client:load />

  • #11403 8f7786f Thanks @​Princesseuh! - Fixed a bare < in Astro text being treated as the start of a tag, such as <p>5 < 6 and 7 > 6</p>. As in HTML, a < that cannot open a tag is text and needs no escaping.

  • #11438 3133ffa Thanks @​Princesseuh! - Fixed #8294: an Astro expression holding only a comment is no longer reported as a parse error, which also stopped the whole file from being formatted.

    <div>{/* a note */}</div>
<div class={/* a note */}>x</div>

  • #11403 8f7786f Thanks @​Princesseuh! - Fixed #9165: an empty Astro expression such as <div>{}</div> no longer fails to parse. Astro renders {} as nothing.

  • #11403 8f7786f Thanks @​Princesseuh! - Fixed Astro expressions containing a comment failing to parse.

    <div>{/* block comment */ x}</div>
<div>{/* only a comment */}</div>

  • #11403 8f7786f Thanks @​Princesseuh! - Added support for Astro's fragment shorthand.

    <>
  <p>a</p>
</>

  • #11403 8f7786f Thanks @​Princesseuh! - Fixed an Astro frontmatter block being cut short by a closing tag inside a string or comment.

    ---
const a = "</script>";
// </script> in a comment
---

  • #11403 8f7786f Thanks @​Princesseuh! - Fixed --- being read as an Astro frontmatter fence when markup precedes it. Astro only recognizes frontmatter at the very start of a file, so a file opening with a comment now has no frontmatter, and its --- lines are content.

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

2.5.10

Patch Changes

  • #11403 8f7786f Thanks @​Princesseuh! - Fixed Astro rejecting JavaScript comments between attributes.

    <div /* block comment */ class="something"></div>
<Component /* c */ client:load />

  • #11403 8f7786f Thanks @​Princesseuh! - Fixed a bare < in Astro text being treated as the start of a tag, such as <p>5 < 6 and 7 > 6</p>. As in HTML, a < that cannot open a tag is text and needs no escaping.

  • #11438 3133ffa Thanks @​Princesseuh! - Fixed #8294: an Astro expression holding only a comment is no longer reported as a parse error, which also stopped the whole file from being formatted.

    <div>{/* a note */}</div>
<div class={/* a note */}>x</div>

  • #11403 8f7786f Thanks @​Princesseuh! - Fixed #9165: an empty Astro expression such as <div>{}</div> no longer fails to parse. Astro renders {} as nothing.

  • #11403 8f7786f Thanks @​Princesseuh! - Fixed Astro expressions containing a comment failing to parse.

    <div>{/* block comment */ x}</div>
<div>{/* only a comment */}</div>

  • #11403 8f7786f Thanks @​Princesseuh! - Added support for Astro's fragment shorthand.

    <>
  <p>a</p>
</>

  • #11403 8f7786f Thanks @​Princesseuh! - Fixed an Astro frontmatter block being cut short by a closing tag inside a string or comment.

    ---
const a = "</script>";
// </script> in a comment
---

  • #11403 8f7786f Thanks @​Princesseuh! - Fixed --- being read as an Astro frontmatter fence when markup precedes it. Astro only recognizes frontmatter at the very start of a file, so a file opening with a comment now has no frontmatter, and its --- lines are content.

    <!-- c -->

... (truncated)

Commits

Updates @types/node from 22.20.1 to 26.2.0

Commits

Updates @vitest/coverage-v8 from 3.2.7 to 4.1.11

Release notes

Sourced from @​vitest/coverage-v8'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

Updates tsdown from 0.21.4 to 0.22.14

Release notes

Sourced from tsdown's releases.

v0.22.14

   🚀 Features

  • Add CLI build concurrency option  -  by @​sxzz and Jeroen Zwartepoorte (8a14c)
    View changes on GitHub

v0.22.13

   🚀 Features

  • deps: Support neverBundle: true to externalize all dependencies  -  by @​sxzz (d30a7)

   🐞 Bug Fixes

    View changes on GitHub

v0.22.12

   🚨 Breaking Changes

    View changes on GitHub

v0.22.11

   🚀 Features

    View changes on GitHub

v0.22.10

   🚀 Features

   🐞 Bug Fixes

    View changes on GitHub

v0.22.9

   🚀 Features

   🐞 Bug Fixes

... (truncated)

Commits
  • ff3bdbd chore: release v0.22.14
  • 8a14c35 feat: add CLI build concurrency option
  • 0525465 docs: add note about cjsDefault only applying to explicit entry modules
  • a3a3551 refactor: fix lint
  • 3dec506 refactor: use native Promise.withResolvers
  • e0266c1 docs: add tsdown users image
  • a733505 refactor: upgrade verkit, simplify version parse
  • e5fe2ca style: format
  • 3e1fc63 chore: release v0.22.13
  • a6c8734 chore: upgrade deps
  • Additional commits viewable in compare view

Updates turbo from 2.10.10 to 2.10.11

Release notes

Sourced from turbo's releases.

Turborepo v2.10.11

What's Changed

Changelog

Full Changelog: vercel/turborepo@v2.10.10...v2.10.11

Turborepo v2.10.11-canary.4

What's Changed

Changelog

Full Changelog: vercel/turborepo@v2.10.11-canary.3...v2.10.11-canary.4

Turborepo v2.10.11-canary.3

What's Changed

Changelog

Full Changelog: vercel/turborepo@v2.10.11-canary.2...v2.10.11-canary.3

Turborepo v2.10.11-canary.2

... (truncated)

Commits

Updates typescript from 5.9.3 to 7.0.2

Release notes

Sourced from typescript's releases.

TypeScript 7.0.2

https://devblogs.microsoft.com/typescript/announcing-typescript-7-0/

This tag was originally released at: https://github.com/microsoft/typescript-go/releases/tag/typescript%2Fv7.0.2

TypeScript 6.0.3

For release notes, check out the release announcement blog post.

Downloads are available on:

TypeScript 6.0

For release notes, check out the release announcement blog post.

Downloads are available on:

TypeScript 6.0.1 RC

For release notes, check out the release announcement blog post.

Downloads are available on:

TypeScript 6.0 Beta

For release notes, check out the release announcement.

Downloads are available on:

Commits
  • 1e4744d Merge branch 'main' into ts7-release
  • a5a219cmicrosoft/typescript-go#4558
  • ecfe30d Update status localization
  • 5de25b5 Hide executable name in TypeScript status
  • d7ce74a Show bundled TypeScript version for packaged servers
  • 29be66a Correct TS 7 release version to 7.0.2
  • ed2bd1b Merge branch 'main' into ts7-release
  • 8873075 Bump the github-actions group across 1 directory with 3 updates (microsoft/ty...
  • 9427131 Set up stable / nightly extension split, other prep (microsoft/typescript-go#...
  • d4eaca5microsoft/typescript-go#4549
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by microsoft1es, a new releaser for typescript since your current version.


Updates 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

Updates commander from 13.1.0 to 15.0.0

Release notes

Sourced from commander's releases.

v15.0.0

Commander 15 is ESM only. This is expected to be seamless for ESM consumers, but some CommonJS consumers may hit issues with tooling requiring configuration for ESM-only dependencies. See Migration Tips below.

The release of Commander 15 moves Commander 14 into maintenance. Commander 14 will get security updates for 12 months (to May 2027). For more info see Release Policy.

Added

  • show excess command-arguments in error message (#2384)

Fixed

  • Breaking: only lone --no-* option sets default option value to true, default not implicitly set when define both positive and negative option in either order (#2405)
  • update example to use compatible character for MINGW64 (#2475)

Changed

  • Breaking: migrated Commander implementation from CommonJS to ESM (#2464)
  • Breaking: Commander 15 requires Node.js v22.12.0 or higher (for require(esm)).
  • dev: switch tests from Jest to node:test test runner (#2463)

Deleted

  • Breaking: removed deprecated export of commander/esm.mjs (#2464)

Migration Tips

Commander 15 is ESM only, but this does not mean you need to migrate to ESM to use it. Importing ESM from CommonJS is supported by Node.js, and Bun, and Deno. Hopefully it Just Works for you! However, you may be using a different runtime or some other part of your setup that may not yet natively support importing ESM from CommonJS, such as your testing framework or bundler.

If you have problems using Commander 15 in your environment, one option is stay on Commander 14 for now. Commander 14 will get security updates until May 2027 and things will hopefully improve for your setup in the meantime.

v15.0.0-0

Commander 15 is ESM only. This is expected to be seamless for ESM consumers, but some CommonJS consumers may hit issues with tooling requiring configuration for ESM-only dependencies. See Migration Tips below.

The release of Commander 15 in May 2026 will move Commander 14 into maintenance. Commander 14 will get security updates for 12 months (to May 2027). For more info see Release Policy.

Added

  • show excess command-arguments in error message (#2384)

Fixed

  • Breaking: only lone --no-* option sets default option value to true, default not implicitly set when define both positive and negative option in either order (#2405)
  • update example to use compatible character for MINGW64 (#2475)

... (truncated)

Changelog

Sourced from commander's changelog.

[15.0.0] (2026-05-29)

Commander 15 is ESM only. This is expected to be seamless for ESM consumers, but some CommonJS consumers may hit issues with tooling requiring configuration for ESM-only dependencies. See Migration Tips below.

The release of Commander 15 moves Commander 14 into maintenance. Commander 14 will get security updates for 12 months (to May 2027). For more info see Release Policy.

Added

  • show excess command-arguments in error message (#2384)

Fixed

  • Breaking: only lone --no-* option sets default option value to true, default not implicitly set when define both positive and negative option in either order (#2405)
  • update example to use compatible character for MINGW64 (#2475)

Changed

  • Breaking: migrated Commander implementation from CommonJS to ESM (#2464)
  • Breaking: Commander 15 requires Node.js v22.12.0 or higher (for require(esm)).
  • dev: switch tests from Jest to node:test test runner (#2463)

Deleted

  • Breaking: removed deprecated export of commander/esm.mjs (#2464)

Migration Tips

Commander 15 is ESM only, but this does not mean you need to migrate to ESM to use it. Importing ESM from CommonJS is supported by Node.js, and Bun, and Deno. Hopefully it Just Works for you! However, you may be using a different runtime or some other part of your setup that may not yet natively support importing ESM from CommonJS, such as your testing framework or bundler.

If you have problems using Commander 15 in your environment, one option is stay on Commander 14 for now. Commander 14 will get security updates until May 2027 and things will hopefully improve for your setup in the meantime.

[15.0.0-0] (2026-02-22)

(Released as 15.0.0)

[14.0.3] (2026-01-31)

Added

  • Release Policy document (#2462)

Changes

  • old major versions now supported for 12 months instead of just previous major version, to give predictable end-of-life date (#2462)
  • clarify typing for deprecated callback parameter to .outputHelp() (#2427)

... (truncated)

Commits

Updates @types/react-dom from 19.2.4 to 19.2.5

Commits

Updates @vitejs/plugin-react from 4.7.0 to 6.1.0

Release notes

Sourced from @​vitejs/plugin-react's releases.

plugin-react@6.1.0

Add experimental native React Compiler support (#1419)

Add experimental native React Compiler support.

You can use it by installing oxc-transform-react and enabling it via the compiler option:

npm install -D oxc-transform-react
import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'
export default defineConfig({
plugins: [
react({ compiler: true })
]
})

plugin-react@6.0.5

Fixed the react compiler preset filter to be linear (#1353)

The improved filter in v6.0.3 was non-linear and caused a performance regression (#1349). The filter was changed to be linear to avoid that.

plugin-react@6.0.4

Fixed $RefreshSig$ is not defined error when running vite dev with NODE_ENV=production

When running vite dev with NODE_ENV=production, the app errored with $RefreshSig$ is not defined. This error is now fixed.

plugin-react@6.0.3

No release notes provided.

plugin-react@6.0.2

Allow all options in reactCompilerPreset (#1189)

This is a type only change. Only compilationMode and target options were available for reactCompilerPreset.

plugin-react@6.0.1

Expand @rolldown/plugin-babel peer dep range (#1146)

Expanded @rolldown/plugin-babel peer dep range to include ^0.2.0.

plugin-react@6.0.0

Remove Babel Related Features (#1123)

Vite 8+ can handle React Refresh Transform by Oxc and doesn't need Babel for it. With that, there are no transform applied that requires Babel. To reduce the installation size of this plugin, babel is no longer a dependency of this plugin and the related features are removed.

If you are using Babel, you can use @rolldown/plugin-babel together with this plugin:

... (truncated)

Changelog

Sourced from @​vitejs/plugin-react's changelog.

Description has been truncated

@dependabot
chore(deps-dev): bump the development-tooling group across 1 director…
70257a8 
…y with 13 updates

Bumps the development-tooling group with 13 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@biomejs/biome](https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome) | `2.5.8` | `2.5.10` |
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `22.20.1` | `26.2.0` |
| [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) | `3.2.7` | `4.1.11` |
| [tsdown](https://github.com/rolldown/tsdown) | `0.21.4` | `0.22.14` |
| [turbo](https://github.com/vercel/turborepo) | `2.10.10` | `2.10.11` |
| [typescript](https://github.com/microsoft/TypeScript) | `5.9.3` | `7.0.2` |
| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `3.2.7` | `4.1.11` |
| [commander](https://github.com/tj/commander.js) | `13.1.0` | `15.0.0` |
| [@types/react-dom](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react-dom) | `19.2.4` | `19.2.5` |
| [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/tree/HEAD/packages/plugin-react) | `4.7.0` | `6.1.0` |
| [jsdom](https://github.com/jsdom/jsdom) | `26.1.0` | `30.0.1` |
| [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | `7.3.6` | `8.2.2` |
| [@testcontainers/postgresql](https://github.com/testcontainers/testcontainers-node) | `11.14.0` | `12.1.0` |



Updates `@biomejs/biome` from 2.5.8 to 2.5.10
- [Release notes](https://github.com/biomejs/biome/releases)
- [Changelog](https://github.com/biomejs/biome/blob/main/packages/@biomejs/biome/CHANGELOG.md)
- [Commits](https://github.com/biomejs/biome/commits/@biomejs/biome@2.5.10/packages/@biomejs/biome)

Updates `@types/node` from 22.20.1 to 26.2.0
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

Updates `@vitest/coverage-v8` 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/coverage-v8)

Updates `tsdown` from 0.21.4 to 0.22.14
- [Release notes](https://github.com/rolldown/tsdown/releases)
- [Commits](rolldown/tsdown@v0.21.4...v0.22.14)

Updates `turbo` from 2.10.10 to 2.10.11
- [Release notes](https://github.com/vercel/turborepo/releases)
- [Changelog](https://github.com/vercel/turborepo/blob/main/RELEASE.md)
- [Commits](vercel/turborepo@v2.10.10...v2.10.11)

Updates `typescript` from 5.9.3 to 7.0.2
- [Release notes](https://github.com/microsoft/TypeScript/releases)
- [Commits](microsoft/TypeScript@v5.9.3...v7.0.2)

Updates `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)

Updates `commander` from 13.1.0 to 15.0.0
- [Release notes](https://github.com/tj/commander.js/releases)
- [Changelog](https://github.com/tj/commander.js/blob/master/CHANGELOG.md)
- [Commits](tj/commander.js@v13.1.0...v15.0.0)

Updates `@types/react-dom` from 19.2.4 to 19.2.5
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react-dom)

Updates `@vitejs/plugin-react` from 4.7.0 to 6.1.0
- [Release notes](https://github.com/vitejs/vite-plugin-react/releases)
- [Changelog](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite-plugin-react/commits/plugin-react@6.1.0/packages/plugin-react)

Updates `jsdom` from 26.1.0 to 30.0.1
- [Release notes](https://github.com/jsdom/jsdom/releases)
- [Commits](jsdom/jsdom@v26.1.0...v30.0.1)

Updates `vite` from 7.3.6 to 8.2.2
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v8.2.2/packages/vite)

Updates `@testcontainers/postgresql` from 11.14.0 to 12.1.0
- [Release notes](https://github.com/testcontainers/testcontainers-node/releases)
- [Commits](testcontainers/testcontainers-node@v11.14.0...v12.1.0)

---
updated-dependencies:
- dependency-name: "@biomejs/biome"
  dependency-version: 2.5.10
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: development-tooling
- dependency-name: "@types/node"
  dependency-version: 26.2.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: development-tooling
- dependency-name: "@vitest/coverage-v8"
  dependency-version: 4.1.11
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: development-tooling
- dependency-name: tsdown
  dependency-version: 0.22.14
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development-tooling
- dependency-name: turbo
  dependency-version: 2.10.11
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: development-tooling
- dependency-name: typescript
  dependency-version: 7.0.2
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: development-tooling
- dependency-name: vitest
  dependency-version: 4.1.11
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: development-tooling
- dependency-name: commander
  dependency-version: 15.0.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: development-tooling
- dependency-name: "@types/react-dom"
  dependency-version: 19.2.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: development-tooling
- dependency-name: "@vitejs/plugin-react"
  dependency-version: 6.1.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: development-tooling
- dependency-name: jsdom
  dependency-version: 30.0.1
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: development-tooling
- dependency-name: vite
  dependency-version: 8.2.2
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: development-tooling
- dependency-name: "@testcontainers/postgresql"
  dependency-version: 12.1.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: development-tooling
...

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 Aug 27, 2026
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 27, 2026
baixiaohang
baixiaohang requested changes Aug 27, 2026
View reviewed changes

@baixiaohang baixiaohang left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Recommendation: request changes

  • Rationale: The grouped major toolchain update breaks the declared Node 22.13 support boundary, the CLI package smoke path, and the existing Web regression suite on this exact head.

Risk level: A

  • Path baseline: includes apps/cli/package.json -> A
  • Semantic lift: the dependency-only diff changes release packaging, deterministic test behavior, and the supported runtime matrix; A remains the highest level.

PR summary

  • Author / repo: dependabot[bot] / first-tree-ai/opentag
  • Problem: Keep contributor build, type-check, test, and packaging workflows current while preserving the supported OpenTag CLI and Web development experience.
  • Approach: Upgrade 13 development-tooling dependencies together and regenerate the workspace lockfile, without intended product behavior changes.
  • Impacted modules: root build/test tooling, CLI packaging, Web build/test environment, and Server integration-test infrastructure.

Review findings
❌ 1. Preserve the declared Node 22.13 compatibility boundary. The changed jsdom@30.0.1 already makes the Node 22.13 CI install fail because it requires Node ^22.22.2, and the new tsdown and Testcontainers lines also require newer Node 22 minors. Either retain versions compatible with ^22.13.0, or intentionally update every affected engine declaration and compatibility job as one contract change. [R5 / apps/web/package.json:28, package.json:26, packages/server/package.json:49]
❌ 2. Regenerate the shipped CLI third-party notices for Commander 15. Both Checks and CLI Pack Smoke fail because apps/cli/THIRD_PARTY_NOTICES still records commander@13.1.0 while the packed bundle contains commander@15.0.0. [R5 / apps/cli/package.json:56]
❌ 3. Resolve the Web test-environment regression introduced by this major upgrade. The Node 26 job reaches the suite but three existing accessibility-name assertions now see concatenated names such as NameReviewer and Claude CodeUnavailable; preserve the intended accessible names and regression assertions, or keep a compatible test environment until the behavior is deliberately migrated. [R5 / apps/web/package.json:28]

Action taken

  • Submitted request changes on head 70257a8435747031f9753f8b09c3039dde8183bf.

yuezengwu
yuezengwu requested changes Aug 27, 2026
View reviewed changes

@yuezengwu yuezengwu left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Reviewed exact head 70257a8435747031f9753f8b09c3039dde8183bf.

Request changes. This grouped major toolchain bump is not migration-complete. The base SHA 4f46b2369a60063b3960c9694ed11a31869825ee passed the required jobs; this head breaks the declared runtime contract and multiple repository/release gates.

Blocking findings:

  1. Preserve or deliberately revise the full Node support contract. Root and CLI still advertise ^22.13.0 || ^24.0.0 || ^26.0.0, but jsdom@30.0.1 requires ^22.22.2 || ^24.15.0 || >=26; the new tsdown/Testcontainers chain also raises Node floors. CI fails installing on Node 22.13, and pnpm install --frozen-lockfile --config.engine-strict=true also fails locally on Node 24.7. Either retain compatible versions or update every engine declaration, build target, compatibility job, and release expectation as one intentional contract change. [package.json:7-9, apps/cli/package.json:41-43, apps/web/package.json:28, packages/server/package.json:49]

  2. Regenerate checked-in tooling/release metadata. pnpm check and CLI Pack Smoke fail because the shipped THIRD_PARTY_NOTICES still records Commander 13 while the package now bundles Commander 15. Regenerate it, and align the Biome schema URL (still 2.5.8) with Biome 2.5.10. [apps/cli/THIRD_PARTY_NOTICES:5, apps/cli/package.json:56, biome.json:2]

  3. Complete the TypeScript 7 / Node types / Vite 8 migration. pnpm typecheck fails at packages/client/src/__tests__/agent-api.test.ts:275,371 because Node 26 types widen fetch inputs to string | Request | URL, and at apps/web/vite.config.ts:14 because the current defineConfig import does not accept the test key. The base head typechecks, so these are introduced by this bump.

  4. Resolve the jsdom 30 accessible-name regressions. pnpm test and the Node 26 job fail 3/325 Web tests: expected names such as Name Reviewer and Claude Code Unavailable become NameReviewer and Claude CodeUnavailable. Preserve the intended accessible names/assertions or keep a compatible test environment until the change is deliberately migrated. [apps/web/src/__tests__/app.test.tsx:1362,2339,2397]

  5. Migrate the enforced Vitest coverage gate. The focused Agent Runtime suite passes all 289 tests, but test:agent-runtime:coverage now fails its required 100% thresholds at statements 99.36%, branches 99.08%, functions 96.07%, and lines 99.87%. Vitest 4 documents changed V8 AST coverage remapping and expected report changes; update tests/ignore hints/config with a justified migration, or retain Vitest 3 until the gate passes. [packages/client/vitest.agent-runtime.config.ts:29-56; https://vitest.dev/guide/migration.html#v8-code-coverage-major-changes]

Validation on Node 24.7 / pnpm 10.12.1:

  • PASS: frozen install (non-strict), pnpm build, git diff --check, server integration (190 tests), and CI Container Smoke.
  • FAIL: strict engine install; pnpm check; pnpm typecheck; pnpm test; root coverage; focused 100% coverage; CLI pack smoke. Current CI likewise has 5 failed jobs and only Container Smoke passing.
  • Lockfile/importer consistency was checked across all five changed files. Updated direct package licenses are MIT/Apache-compatible. pnpm audit still reports 1 high and 5 moderate advisories in unchanged production resolution paths; I found no new advisory attributable to these 13 updated direct packages.

No closing issue is associated with this PR. Do not merge until the declared runtime, packaging, typecheck, regression, and coverage gates are green on one exact head.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@baixiaohang baixiaohang baixiaohang requested changes
@yuezengwu yuezengwu yuezengwu requested changes

Requested changes must be addressed to merge this pull request.

Assignees

No one assigned

Labels

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

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@baixiaohang @yuezengwu