chore(deps): bump NestJS stack and Prisma within current majors

[pashidlos]

Summary

• Bump NestJS 11 packages, Prisma 6, and axios to latest compatible versions
• Regenerate package-lock.json (replaces the stale express/nestjs Dependabot PRs from 2024–2025)
• npm audit: 71 → 36 findings; critical 2 → 0

Why

Open Dependabot PRs (#309–#328) target an old Nest/express stack and all conflict on package-lock.json. Current master is already on Nest 11, so one fresh semver-safe bump is cleaner than merging those.

Test plan

• npm run build
• npm test -- --runInBand (32 suites / 175 tests)
• CI green on this PR
• After merge, close stale Dependabot PRs: Bump send, @nestjs/platform-express and express #309 Bump body-parser, @nestjs/platform-express and express #310 Bump webpack and @nestjs/cli #313 Bump path-to-regexp, @nestjs/core, @nestjs/platform-express, @nestjs/swagger and express #314 Bump cross-spawn from 7.0.3 to 7.0.6 #318 Bump express and @nestjs/platform-express #322 Bump serialize-javascript from 6.0.1 to 6.0.2 #328

Made with Cursor

[coderabbitai]

Warning

Review limit reached

@pashidlos, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 38 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 93df6136-59d2-4cfe-9671-1d8015a65d21

📥 Commits

Reviewing files that changed from the base of the PR and between 190e17c and 993c2a5.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json, !**/package-lock.json

📒 Files selected for processing (1)

• package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/deps-bump-nestjs-security

---

_{Comment @coderabbitai help to get the list of available commands.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud