[Snyk] Fix for 3 vulnerabilities

[riddhi-desai]

Snyk has created this PR to fix 3 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Always-Incorrect Control Flow Implementation SNYK-JS-NESTJSCORE-15682556	125
	Missing Release of Resource after Effective Lifetime SNYK-JS-MULTER-15365916	93
	Incomplete Cleanup SNYK-JS-MULTER-15365918	93

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[riddhi-desai]

This major version upgrade to NestJS v11 introduces significant breaking changes that require developer action, primarily related to environment updates and routing syntax.

Key Breaking Changes:

• Node.js Requirement: Support for Node.js versions 16 and 18 has been dropped. NestJS v11 now requires Node.js v20 or higher. [2]
• Express v5 Integration: @nestjs/platform-express now uses Express v5, which changes the route matching algorithm. This is a code-breaking change.
  • Action Required: Wildcard routes (*) must be updated to use named parameters. For example, a route like @Get('users/*') must be changed to @Get('users/*splat'). [2, 3]
• Dynamic Module Handling: The internal mechanism for identifying and deduplicating dynamic modules has changed from hashing to object references. This may break integration tests where the same dynamic module was imported in multiple places and implicitly treated as a singleton. [2]
• CacheModule Update: If you use @nestjs/cache-manager, it has been upgraded and includes breaking changes in its configuration API. [2, 6]

Recommendation: This upgrade requires code and environment changes. Developers must review their route definitions to ensure they comply with the new Express v5 syntax and verify that their Node.js version is v20 or greater. Review the official migration guide for a complete list of changes.

Source: NestJS v11 Migration Guide

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[sb-benohe]

✅ This PR has been automatically closed

The security issues addressed by this pull request are no longer present in the latest project scan. All vulnerabilities this PR was created to fix have been resolved through other means (e.g., dependency updates, direct fixes, or changes in vulnerability data).

Resolved Issues

• SNYK-JS-MULTER-15365916
• SNYK-JS-MULTER-15365918
• SNYK-JS-NESTJSCORE-15682556

What should I do?

No action is required. If you believe this PR was closed in error, you can reopen it and contact Snyk support.

---

This action was performed automatically by Snyk.