[Snyk] Security upgrade next from 13.4.12 to 15.5.16#99
Conversation
…ns/pnpm-lock.yaml to reduce vulnerabilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-NEXT-16638674
|
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:
Key Breaking Changes in Next.js 14:
Recommendation:
|
⛔ Snyk checks have failed. 2 issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
There was a problem hiding this comment.
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
nextfrom 13.4.12 to 15.5.16 inusage-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/envand 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 withtslib2.8.1,postcss→ 8.4.31,styled-jsx→ 5.1.6,caniuse-lite→ 1.0.30001792). - Add optional
sharp0.34.5 and its platform-specific helper packages, plusdetect-libc,semver, and@img/*packages for image handling in Next 15. - Remove no-longer-needed dependencies
busboy,streamsearch, andzodthat 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
sharpand@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-jsxandpostcsscould 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. |
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.jsonusage-based-subscriptions/pnpm-lock.yamlVulnerabilities that will be fixed with an upgrade:
SNYK-JS-NEXT-16638674
Breaking Change Risk
Important
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