[Snyk] Security upgrade next from 14.2.5 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/supabase/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 improving the security of the project by updating the next dependency within the examples/supabase application. The primary goal is to remediate a high-severity vulnerability, ensuring the application leverages a more secure version of the framework.

Highlights

• Dependency Upgrade: The next dependency has been upgraded from version 14.2.5 to 15.5.10 in the examples/supabase/package.json file.
• Security Vulnerability Fix: This upgrade addresses a high-severity vulnerability (SNYK-JS-NEXT-15104645) identified as 'Allocation of Resources Without Limits or Throttling' in the next package.

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 the next dependency from version 14.2.5 to 15.5.10 to address a security vulnerability. This is a major version upgrade, which introduces potentially breaking changes, as indicated by Snyk. It is crucial to conduct thorough testing to ensure the application continues to function as expected after this upgrade. Most importantly, the pnpm-lock.yaml file has not been updated. This must be done manually by running pnpm install and committing the resulting changes to ensure the vulnerability is actually remediated.

[gemini-code-assist]

This change updates the next dependency, but the pnpm-lock.yaml file has not been updated. As noted in the pull request description, the automatic update of the lockfile failed. To ensure the security vulnerability is resolved and the new dependency version is used, you must manually update the lockfile by running pnpm install and committing the updated pnpm-lock.yaml file.