Skip to content

[Snyk] Security upgrade next from 13.4.12 to 15.5.16#99

Open
snyk-io[bot] wants to merge 1 commit into
masterfrom
snyk-fix-18022d7d8c3a25aa6805a4f2eb85ccdb
Open

[Snyk] Security upgrade next from 13.4.12 to 15.5.16#99
snyk-io[bot] wants to merge 1 commit into
masterfrom
snyk-fix-18022d7d8c3a25aa6805a4f2eb85ccdb

Conversation

@snyk-io
Copy link
Copy Markdown

@snyk-io snyk-io Bot commented May 12, 2026

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the pnpm dependencies of this project.

Snyk changed the following file(s):

  • usage-based-subscriptions/package.json
  • usage-based-subscriptions/pnpm-lock.yaml

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Allocation of Resources Without Limits or Throttling
SNYK-JS-NEXT-16638674
  710  

Breaking Change Risk

Merge Risk: High

Notice: This assessment is enhanced by AI.


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

…ns/pnpm-lock.yaml to reduce vulnerabilities

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-NEXT-16638674
@snyk-io
Copy link
Copy Markdown
Author

snyk-io Bot commented May 12, 2026

Merge Risk: High

This is a major upgrade, spanning two major versions from Next.js 13 to 15. It introduces significant breaking changes that require mandatory code modifications, dependency updates, and careful review of application behavior, particularly around caching.

Key Breaking Changes in Next.js 15:

  • Caching is Now Opt-In: This is the most critical behavioral change. In v15, fetch requests, GET Route Handlers, and client-side navigations are no longer cached by default. [5, 6] You must explicitly opt into caching where needed (e.g., fetch(..., { cache: 'force-cache' })) to avoid performance regressions or unexpected dynamic behavior. [15]
  • Asynchronous Request APIs: Previously synchronous APIs like cookies(), headers(), draftMode(), params, and searchParams are now asynchronous and must be awaited. [4, 5, 15] A codemod is available to help automate this migration: npx @next/codemod@canary next-async-request-api. [5]
  • React 19 Required: Next.js 15 requires React 19 (or its RC version), which involves updating react and react-dom dependencies. [2, 6]

Key Breaking Changes in Next.js 14:

  • Node.js Version: The minimum required Node.js version was raised to 18.17. [7, 8]
  • next export Removed: The next export command has been removed. For static exports, you must now use the output: 'export' option in your next.config.js file. [7, 8]
  • Import Changes: The @next/font package is removed in favor of the built-in next/font. The ImageResponse import was moved from next/server to next/og. Codemods are available for both changes. [7, 8]

Recommendation:
This upgrade is high-risk and requires significant developer action.

  1. Run the provided codemods to handle API and import changes. [5, 7]
  2. Thoroughly review your application's data fetching and caching strategy to explicitly opt-in where caching is needed. [5]
  3. Update Node.js to at least version 18.17 and upgrade React dependencies to v19. [7, 2]
  4. Test your application extensively, paying close attention to data freshness on navigation and API route responses.

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

@snyk-io
Copy link
Copy Markdown
Author

snyk-io Bot commented May 12, 2026

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

Status Scan Engine Critical High Medium Low Total (2)
Open Source Security 0 2 0 0 2 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

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

Copy link
Copy Markdown

@hivel-marco hivel-marco Bot left a comment

Choose a reason for hiding this comment

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

PR Complexity Score: 1.8 - Trivial

View Breakdown
  • Lines Changed: 449
  • Files Changed: 2
  • Complexity Added: 0
  • Raw Score: 14.98
Overview

This PR upgrades the usage-based-subscriptions app from Next.js 13.4.12 to 15.5.16 and refreshes the dependency lockfile accordingly.
It aligns related packages (like next-superjson, @swc/helpers, styled-jsx, and postcss) with the new Next.js version and updates pnpm lockfile settings.
The change also introduces optional image-processing dependencies (sharp and associated platform binaries) that are now used by newer Next.js versions.

Key Changes
  • Bump next from 13.4.12 to 15.5.16 in usage-based-subscriptions, requiring Node.js >=18.18.0 / >=20 and widening React/ReactDOM peer ranges.
  • Update the pnpm lockfile to reflect the new Next.js version, including new @next/env and all platform-specific @next/swc-* binaries at 15.5.16.
  • Refresh transitive dependencies to versions compatible with Next 15 (e.g. @swc/helpers → 0.5.15 with tslib 2.8.1, postcss → 8.4.31, styled-jsx → 5.1.6, caniuse-lite → 1.0.30001792).
  • Add optional sharp 0.34.5 and its platform-specific helper packages, plus detect-libc, semver, and @img/* packages for image handling in Next 15.
  • Remove no-longer-needed dependencies busboy, streamsearch, and zod that were previously pulled in by Next 13.
  • Configure pnpm lockfile settings (autoInstallPeers: true, excludeLinksFromLockfile: false) to align with current tooling behavior.
Risks & Considerations
  • Next.js 15 introduces breaking and behavioral changes relative to 13; the app should be regression-tested thoroughly (routing, data fetching, middleware, and any custom server logic).
  • New Node.js engine constraints (>=18.18.0 / >=20) may break environments still on older Node versions.
  • Optional sharp and @img/* binaries may cause install or build issues on unusual platforms/architectures; CI and deployment environments should be verified.
  • New or updated peer dependencies (e.g. optional @playwright/test, babel-plugin-react-compiler) might affect tooling if added later; ensure versions remain compatible.
  • Changes to styled-jsx and postcss could subtly affect styling or CSS processing; visual and styling checks are recommended.
File-level change summary
File Change summary
usage-based-subscriptions/package.json Bumps the Next.js dependency from version 13.4.12 to 15.5.16 for the usage-based-subscriptions app.
usage-based-subscriptions/pnpm-lock.yaml Regenerates the lockfile for the Next.js 15.5.16 upgrade, updating/transitively adding/removing dependencies and pnpm settings.

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.

0 participants