fix(deps): revert @swc/cli to ^0.7.0 due to @nestjs/cli incompatibility

[renovate]

Description

Reverts @swc/cli from ^0.8.0 back to ^0.7.0 in backend/package.json due to peer dependency incompatibilities introduced by the ^0.8.0 upgrade.

@swc/cli@0.8.x is incompatible with the current @nestjs/cli@11.x for two reasons:

1. @nestjs/cli@11.0.17 only lists @swc/cli up to ^0.7.0 in its optional peer dependencies — ^0.8.0 is not supported.
2. @swc/cli@0.8.1 requires chokidar@^5.0.0 as a peer dependency, but @nestjs/cli depends on chokidar@4.0.3, causing an irreconcilable conflict that prevents npm install from resolving.

Dependency changes:

• backend/package.json: @swc/cli reverted from ^0.8.0 → ^0.7.0
• backend/package-lock.json: restored to the original pre-upgrade state (locks @swc/cli at 0.7.10 with all other dependencies unchanged)

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

• No new tests are required
• Manual tests (description below)

Verified that npm ci --dry-run resolves without errors with @swc/cli reverted to ^0.7.0 and the lock file restored to its original state.

Checklist

• I have read the CONTRIBUTING doc
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have already been accepted and merged

Further comments

The @swc/cli@^0.8.0 upgrade can be reconsidered once @nestjs/cli adds support for @swc/cli@0.8.x in its peer dependencies and the chokidar major version conflict is resolved upstream.

The package-lock.json is restored to its exact pre-upgrade state rather than regenerated, to avoid unintended updates to other transitive dependencies (e.g. hono, magicast) that would cause npm ci sync errors in CI.

---

Thanks for the PR!

Deployments, as required, will be available below:

• Frontend
• Backend

Please create PRs in draft mode. Mark as ready to enable:

• Analysis Workflow

After merge, new images are deployed in:

• Merge Workflow

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: backend/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @nestjs/cli@11.0.17
npm error Found: @swc/cli@0.8.1
npm error node_modules/@swc/cli
npm error   dev @swc/cli@"^0.8.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional @swc/cli@"^0.1.62 || ^0.3.0 || ^0.4.0 || ^0.5.0 || ^0.6.0 || ^0.7.0" from @nestjs/cli@11.0.17
npm error node_modules/@nestjs/cli
npm error   @nestjs/cli@"^11.0.2" from the root project
npm error
npm error Conflicting peer dependency: @swc/cli@0.7.10
npm error node_modules/@swc/cli
npm error   peerOptional @swc/cli@"^0.1.62 || ^0.3.0 || ^0.4.0 || ^0.5.0 || ^0.6.0 || ^0.7.0" from @nestjs/cli@11.0.17
npm error   node_modules/@nestjs/cli
npm error     @nestjs/cli@"^11.0.2" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-04-01T02_40_23_577Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-04-01T02_40_23_577Z-debug-0.log

[DerekRoberts]

@copilot Can you fix this dependency PR?

[Copilot]

@copilot Can you fix this dependency PR?

Reverted @swc/cli back to ^0.7.0 in commit 2c02145.

@swc/cli@0.8.x is incompatible with @nestjs/cli@11.x for two reasons:

1. @nestjs/cli@11.0.17 only lists @swc/cli up to ^0.7.0 in its peer dependencies
2. @swc/cli@0.8.1 requires chokidar@^5.0.0, but @nestjs/cli depends on chokidar@4.0.3, causing an irreconcilable peer dependency conflict

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[socket-security]

No dependency changes detected. Learn more about Socket for GitHub.

👍 No dependency changes detected in pull request

[DerekRoberts]

@copilot Analysis / Backend Tests are failing. Please fix in this PR.

[Copilot]

@copilot Analysis / Backend Tests are failing. Please fix in this PR.

Fixed in commit 2a3e607. The previous fix ran npm install --package-lock-only which inadvertently updated hono and magicast beyond just @swc/cli, causing npm ci to fail with a sync error. Since the renovate commit never modified package-lock.json, restoring it to the base commit state was sufficient — npm ci --dry-run now passes cleanly.