Skip to content

[Snyk] Security upgrade next from 14.2.14 to 15.5.10#95

Open
decause-gov wants to merge 1 commit intomainfrom
snyk-fix-ce37dc8ad230826f381b808cbf981822
Open

[Snyk] Security upgrade next from 14.2.14 to 15.5.10#95
decause-gov wants to merge 1 commit intomainfrom
snyk-fix-ce37dc8ad230826f381b808cbf981822

Conversation

@decause-gov
Copy link
Copy Markdown

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

@decause-gov
Copy link
Copy Markdown
Author

Merge Risk: High

This major version upgrade to Next.js 15 introduces significant breaking changes, including a mandatory update to React 19 and fundamental shifts in core API patterns and caching behavior. Careful migration and testing are required.

Highlights:

  • React 19 Required: The minimum versions for react and react-dom are now 19. This may cause peer dependency conflicts with other libraries. [6, 12]
  • Async APIs: Previously synchronous APIs like cookies(), headers(), and params are now asynchronous and must be awaited. A codemod is available to help automate this. [6, 9]
  • Caching Defaults Changed: fetch requests and GET Route Handlers are no longer cached by default; they now default to 'no-store'. You must explicitly add cache: 'force-cache' or other caching strategies where needed. [5, 9]

Source: Next.js documentation
Recommendation: Review the official Next.js 15 upgrade guide, run the provided codemods to update async APIs, and thoroughly test your application for issues related to React 19 dependencies and new caching behavior.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

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