Skip to content

chore: defer @swc/cli@0.8.0 upgrade due to ecosystem incompatibility #2622

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
DerekRoberts wants to merge 1 commit into from
Closed

chore: defer @swc/cli@0.8.0 upgrade due to ecosystem incompatibility #2622

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 27 additions & 0 deletions docs/UPGRADE_NOTES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
# Package Upgrade Notes

## @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`
Comment on lines +3 to +7
Copy link

Copilot AI Feb 10, 2026

Choose a reason for hiding this comment

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

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.

Suggested change
## @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`

Copilot uses AI. Check for mistakes.

### Why It Cannot Proceed

1. **@swc/cli@0.8.0** requires `chokidar@^5.0.0` as a peer dependency
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`
Comment on lines +12 to +13
Copy link

Copilot AI Feb 10, 2026

Choose a reason for hiding this comment

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

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.

Suggested change
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`

Copilot uses AI. Check for mistakes.

### Solution

Defer this upgrade until:
- `@nestjs/cli` releases a new version (v11.1.0, v12.0.0, etc.) that explicitly declares support for `@swc/cli@0.8.0`
- Then upgrade both `@nestjs/cli` and `@swc/cli` together

### Why Not Use Workarounds?

- ❌ `legacy-peer-deps=true`: Masks real incompatibilities, risks runtime failures
- ❌ Back-compatibility fixes: Would require downgrading `@swc/cli`, defeating the purpose
- ❌ Overrides without proper peer resolution: Creates brittle, non-reproducible builds

The proper approach is to wait for upstream library support.
Loading