chore: defer @swc/cli@0.8.0 upgrade due to ecosystem incompatibility#2622
chore: defer @swc/cli@0.8.0 upgrade due to ecosystem incompatibility#2622DerekRoberts wants to merge 1 commit intomainfrom
Conversation
…lity - @swc/cli@0.8.0 requires chokidar@5.x - @nestjs/cli v11.0.x does not yet support @swc/cli@0.8.0 - Awaiting @nestjs/cli release that declares @swc/cli@0.8.0 compatibility - Deferring to later review when ecosystem is ready
|
Not ready yet. |
There was a problem hiding this comment.
Pull request overview
Adds documentation explaining why the Renovate upgrade of @swc/cli to 0.8.0 is being deferred due to peer-dependency incompatibility with the currently supported @nestjs/cli range.
Changes:
- Added
docs/UPGRADE_NOTES.mddescribing the deferred@swc/cli@0.8.0upgrade and rationale. - Documented why common workarounds (e.g., legacy peer dep behavior / overrides) are not recommended here.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ## @swc/cli Upgrade - Deferred | ||
|
|
||
| **Status:** Deferred until ecosystem compatibility improves | ||
|
|
||
| **Issue:** Renovate PR attempted to upgrade `@swc/cli` from `^0.7.0` to `^0.8.0` |
There was a problem hiding this comment.
This note is written as if the repository has a single Node project, but @nestjs/cli/@swc/cli only appear under backend/. Consider explicitly calling out the impacted workspace/path (e.g., backend/package.json) so future readers don’t assume this applies to the frontend or other packages.
| ## @swc/cli Upgrade - Deferred | |
| **Status:** Deferred until ecosystem compatibility improves | |
| **Issue:** Renovate PR attempted to upgrade `@swc/cli` from `^0.7.0` to `^0.8.0` | |
| ## backend/: @swc/cli Upgrade - Deferred | |
| **Status:** Deferred until ecosystem compatibility improves | |
| **Issue:** Renovate PR against `backend/package.json` attempted to upgrade `@swc/cli` from `^0.7.0` to `^0.8.0` |
| 2. **@nestjs/cli** latest version (11.0.16) only declares compatibility with `@swc/cli@^0.1-0.7.x` | ||
| 3. No newer version of `@nestjs/cli` exists yet that supports `@swc/cli@0.8.0` |
There was a problem hiding this comment.
The statements about the "latest version (11.0.16)" and "No newer version exists yet" will become stale as soon as upstream releases. Consider making this time-bound (e.g., "as of ") and/or citing the actual peerDependency range that blocks the upgrade (from the @nestjs/cli package manifest) instead of asserting what the latest version is.
| 2. **@nestjs/cli** latest version (11.0.16) only declares compatibility with `@swc/cli@^0.1-0.7.x` | |
| 3. No newer version of `@nestjs/cli` exists yet that supports `@swc/cli@0.8.0` | |
| 2. As of 2025-02-10, **@nestjs/cli** version 11.0.16 declares compatibility only with `@swc/cli@^0.1-0.7.x` (per its `peerDependencies`) | |
| 3. As of 2025-02-10, no released version of `@nestjs/cli` declares support for `@swc/cli@0.8.0` in its `peerDependencies` |
Summary
The Renovate PR to upgrade
@swc/clifrom ^0.7.0 to ^0.8.0 cannot proceed at this time due to ecosystem incompatibility.Root Cause
chokidar@^5.0.0as a peer dependency@swc/cli@^0.1-0.7.x@nestjs/cliversion exists yet that supports@swc/cli@0.8.0Why Workarounds Won't Work
legacy-peer-deps=true- masks real incompatibilities, risks runtime failures@swc/cli- defeats the purpose of the upgradeSolution
Defer this upgrade until
@nestjs/clireleases a version (v11.1.0 or later) that explicitly declares compatibility with@swc/cli@0.8.0. At that point, we can upgrade both packages together.See
docs/UPGRADE_NOTES.mdfor details.Thanks for the PR!
Deployments, as required, will be available below:
Please create PRs in draft mode. Mark as ready to enable:
After merge, new images are deployed in: