[Snyk] Security upgrade next from 12.1.6 to 15.5.10

[q1blue]

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
	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 @q1blue, 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 automates a critical security update for the project's next dependency. The primary goal is to mitigate a high-severity vulnerability by upgrading the next package to a secure version, thereby enhancing the application's resilience against known exploits related to resource allocation. It ensures the project stays up-to-date with security best practices.

Highlights

• Dependency Upgrade: The next dependency has been upgraded from latest (implicitly 12.1.6) to 15.5.10 in package.json.
• Security Vulnerability Fix: This upgrade addresses a high-severity vulnerability (SNYK-JS-NEXT-15104645) related to 'Allocation of Resources Without Limits or Throttling' found in the next package.
• Manual Intervention Required: The package-lock.json file was not automatically updated and requires manual intervention to ensure consistency and proper dependency resolution.

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 from Snyk upgrades the next package to version 15.5.10 to fix a security vulnerability. While the upgrade is necessary, this PR is incomplete and carries significant risk. As noted in the PR description, the package-lock.json file has not been updated, which is a critical issue that must be resolved by running npm install and committing the lock file. Additionally, this is a major version upgrade from v12 to v15, which is flagged as a breaking change and will require thorough testing to ensure application stability.

[gemini-code-assist]

This upgrade is crucial for security, but this pull request is incomplete and requires manual intervention before merging.

1. package-lock.json is missing: As Snyk noted, the package-lock.json file failed to update. You must run npm install and commit the updated lock file. Without this, the dependency update is not guaranteed, and the vulnerability might remain.
2. Major Breaking Changes: This is a major version jump from next@12 to next@15. This is a significant change that introduces a high risk of breaking changes. Please ensure you thoroughly test the application after applying this upgrade.

Pinning the version is a good practice compared to using latest, but the associated risks and necessary follow-up actions must be addressed.