[Snyk] Security upgrade next from 14.2.3 to 15.5.10

[iamdrewfortini]

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

Snyk changed the following file(s):

• examples/middleware/package.json

⚠️ Warning

Failed to update the pnpm-lock.yaml, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-JS-NEXT-15104645	149

---

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:

🦉 Allocation of Resources Without Limits or Throttling

[gemini-code-assist]

Summary of Changes

Hello @iamdrewfortini, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, focuses on enhancing the security of the project by updating a critical dependency. The primary goal is to mitigate a high-severity vulnerability found in the next package within the examples/middleware module, ensuring the application benefits from the latest security patches and improvements.

Highlights

• Dependency Upgrade: The next dependency in examples/middleware/package.json has been upgraded from version ^14.2 to ^15.5.10.
• Security Vulnerability Fix: This upgrade addresses a high-severity vulnerability, 'Allocation of Resources Without Limits or Throttling' (SNYK-JS-NEXT-15104645), improving the project's security posture.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, upgrades next from version 14 to 15 to resolve a security vulnerability. While this is an important security fix, upgrading a major version of a framework like Next.js introduces significant breaking changes. The PR is currently incomplete and will likely break the build. I've added a comment highlighting the required updates for peer dependencies like react and react-dom to version 19, as well as the eslint-config-next package. Additionally, as noted in the PR description, the pnpm-lock.yaml file needs to be manually updated after applying these changes.

[gemini-code-assist]

This major version upgrade of Next.js from v14 to v15 introduces breaking changes that require other dependencies to be updated as well:

1. React version (Critical): Next.js 15 requires React 19. The react and react-dom dependencies (and their corresponding @types/ packages) need to be upgraded from ^18 to a compatible React 19 version (e.g., ^19.0.0-rc.0). Without this, the application will not work.

2. ESLint config (High): The eslint-config-next dev dependency should be updated to match the new Next.js version (e.g., 15.5.10) to ensure linting rules are up-to-date and compatible.