Skip to content

[Snyk] Security upgrade next from 14.2.32 to 15.5.10#25

Open
hashim21223445 wants to merge 1 commit into
masterfrom
snyk-fix-939b993e98068a5477edfd310ab82a86
Open

[Snyk] Security upgrade next from 14.2.32 to 15.5.10#25
hashim21223445 wants to merge 1 commit into
masterfrom
snyk-fix-939b993e98068a5477edfd310ab82a86

Conversation

@hashim21223445

Copy link
Copy Markdown
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):

  • examples/ts/nextjs-page-router/package.json
  • examples/ts/nextjs-page-router/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

…-page-router/package-lock.json to reduce vulnerabilities

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-NEXT-15104645
@semanticdiff-com

semanticdiff-com Bot commented Jan 29, 2026

Copy link
Copy Markdown

Review changes with  SemanticDiff

Changed Files
File Status
  examples/ts/nextjs-page-router/package-lock.json  14% smaller
  examples/ts/nextjs-page-router/package.json  0% smaller

@gemini-code-assist

Copy link
Copy Markdown

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 an automated security upgrade for the next framework within the project's examples/ts/nextjs-page-router directory. Initiated by Snyk, the update aims to mitigate a high-severity vulnerability by bumping the next package version from 14.2.32 to 15.5.10. The changes primarily involve modifications to package.json and package-lock.json to reflect the updated core dependency and its associated ecosystem of packages, ensuring the project benefits from the latest security patches and dependency resolutions.

Highlights

  • Next.js Version Upgrade: The next dependency has been upgraded from version 14.2.32 to 15.5.10 in the examples/ts/nextjs-page-router project.
  • Vulnerability Fix: This upgrade addresses a high-severity vulnerability (SNYK-JS-NEXT-15104645) related to 'Allocation of Resources Without Limits or Throttling'.
  • Dependency Updates: Numerous transitive dependencies, including @next/env, various @next/swc-* packages, @swc/helpers, semver, and styled-jsx, have been updated or added/removed to align with the new Next.js version. Notably, sharp and its related @img/* optional dependencies were introduced, while busboy, streamsearch, lru-cache, and yallist were removed.

🧠 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.

@snyk-io

snyk-io Bot commented Jan 29, 2026

Copy link
Copy Markdown

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 gemini-code-assist Bot left a comment

Copy link
Copy Markdown

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 upgrade and may include breaking changes, so thorough testing is recommended. I've also added a suggestion to update the related eslint-config-next package to maintain tooling compatibility.

"dependencies": {
"ccxt": "^4.1.56",
"next": "14.2.32",
"next": "15.5.10",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

With the major upgrade of next, it's good practice to also update related development dependencies. Consider upgrading eslint-config-next in your devDependencies to a version compatible with Next.js 15 (e.g., 15.5.10) to leverage the latest linting rules and avoid potential incompatibilities.

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