Skip to content

[Snyk] Security upgrade next from 14.2.21 to 15.5.10#34

Open
hashim21223445 wants to merge 1 commit intoAndokas2from
snyk-fix-7a89014ba2b13b68ea7b1aa8df34f18c
Open

[Snyk] Security upgrade next from 14.2.21 to 15.5.10#34
hashim21223445 wants to merge 1 commit intoAndokas2from
snyk-fix-7a89014ba2b13b68ea7b1aa8df34f18c

Conversation

@hashim21223445
Copy link
Owner

snyk-top-banner

Snyk has created this PR to fix 1 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
high severity Allocation of Resources Without Limits or Throttling
SNYK-JS-NEXT-15104645
  696  

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

@semanticdiff-com
Copy link

semanticdiff-com bot commented Jan 31, 2026

Review changes with  SemanticDiff

Changed Files
File Status
  package-lock.json  10% smaller
  package.json  0% smaller

@snyk-io
Copy link
Contributor

snyk-io bot commented Jan 31, 2026

Snyk checks have failed. 1 issues have been found so far.

Status Scanner Critical High Medium Low Total (1)
Open Source Security 0 1 0 0 1 issues

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

@gemini-code-assist
Copy link

Summary of Changes

Hello @hashim21223445, I'm Gemini Code Assist1! 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 performs a critical security upgrade for the 'next' framework dependency. It updates the 'next' package to version 15.5.10 to mitigate a high-severity vulnerability related to uncontrolled resource allocation. The changes primarily involve updating the project's dependency lock files to ensure all transitive dependencies are aligned with the new, more secure version of 'next'.

Highlights

  • Security Vulnerability Fix: This pull request addresses a high-severity vulnerability (SNYK-JS-NEXT-15104645) in the 'next' package, identified as 'Allocation of Resources Without Limits or Throttling'.
  • Dependency Upgrade: The 'next' package has been upgraded from version 14.2.21 (locked) to 15.5.10 to incorporate the security fix and other updates.
  • Automated Remediation: This upgrade was automatically generated by Snyk as a security fix pull request.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This PR upgrades next to version 15.5.10 to fix a security vulnerability. This is a major version bump and introduces breaking changes. The most critical change is the new Node.js version requirement: ^18.18.0 || ^19.8.0 || >= 20.0.0. Your environments must be updated to meet this requirement. Additionally, this PR resolves a version mismatch for next that existed between package.json and package-lock.json. Due to the major version upgrade, thorough testing is highly recommended.

Comment on lines 3577 to 3579
"engines": {
"node": ">=18.17.0"
"node": "^18.18.0 || ^19.8.0 || >= 20.0.0"
},

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

The upgrade to next@15 introduces a stricter Node.js version requirement. The required version is now ^18.18.0 || ^19.8.0 || >= 20.0.0, which is an increase from the previous >=18.17.0. This is a significant breaking change that could impact your build and deployment pipelines. All environments must be updated to a compatible Node.js version to avoid failures.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants