This release includes 1 breaking change for platform teams planning a safe upgrade.
✓ No known CVEs patched in this version
Topics
+8 more
Affected surfaces
ReleasePort's take
Light signalPin chokidar to ^4.0.3 to ensure compatibility with Node.js versions 18 and above.
Why it matters: Affects projects using chokidar; pinning guarantees support for Node >=18.
Summary
AI summaryPin chokidar to ^4.0.3 for compatibility with Node >=18.
Changes in this release
| Type | Severity | Summary | CVE |
|---|---|---|---|
| Dependency | Medium |
Pin chokidar to ^4.0.3 for Node >=18 support Pin chokidar to ^4.0.3 for Node >=18 support Source: llm_adapter@2026-07-14 Confidence: low |
— |
| Bugfix | High |
Fix breaking MCP installs caused by chokidar v5 requiring Node >=20.19.0 Fix breaking MCP installs caused by chokidar v5 requiring Node >=20.19.0 Source: granite4.1:30b@2026-07-15-audit Confidence: low |
— |
Full changelog
Fixed
- Pin chokidar to ^4.0.3 — supports Node >=18
- chokidar v5 required Node >=20.19.0, breaking MCP installs in TRAE AI, Antigravity, and other tools that bundle older Node runtimes
Breaking Changes
- Pin chokidar to ^4.0.3 (minimum Node.js version 18) – prevents incompatibility with newer chokidar v5 which requires Node >=20.19.0.
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
Related context
Related tools
Earlier breaking changes
- v1.6.1 Health scores from v1.6.1+ are not directly comparable to earlier versions.
Beta — feedback welcome: [email protected]