[Snyk] Security upgrade @nestjs/graphql from 11.0.0 to 13.4.3

[TheRedHatter]

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

Snyk changed the following file(s):

• package.json

⚠️ Warning

Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Asymmetric Resource Consumption (Amplification) SNYK-JS-WS-17344547	706

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.

[TheRedHatter]

This is a major version upgrade from v11 to v13, introducing significant and mandatory breaking changes. The upgrade spans two major versions (v12 and v13) and requires a substantial migration effort, primarily due to the underlying changes in both the Apollo Server dependency and the NestJS framework itself.

Key Breaking Changes:

• Apollo Server v4+ Migration: The most critical change is the move from apollo-server-express (used with Apollo Server v3) to the @apollo/server package. This is not a direct replacement and requires a complete overhaul of your GraphQL module setup. You must install new dependencies (@apollo/server, @as-integrations/express5) and refactor your GraphQLModule.forRoot() configuration to use the new ApolloDriver.

• NestJS v12+ Framework Changes: This upgrade requires a corresponding upgrade of your NestJS framework to v12 or later. NestJS v12 introduced its own set of breaking changes, including a move to native ESM, which can impact your project's build configuration (tsconfig.json) and overall structure.

• Node.js Version Requirement: NestJS v11 dropped support for Node.js v16 and v18. This upgrade will require you to use Node.js v20 or higher to be compatible with the latest NestJS framework versions.

• Apollo v5 Support: Version 13.2.0 and later introduce support for Apollo Server v5, which may include additional considerations.

Recommendation:
This upgrade cannot be completed with simple package updates. Treat this as a major migration project. You will need to:

1. Upgrade your entire NestJS application to v12 or v13.
2. Update your Node.js version to v20+.
3. Completely reconfigure your GraphQL module implementation according to the latest NestJS documentation, replacing apollo-server-express with @apollo/server and updating the driver configuration.

Source: NestJS GraphQL Documentation

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

[TheRedHatter]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[TheRedHatter]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.