next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 13.4.16 to 13.4.17
1 release in betweenevery note read
Security
38 advisories still affect 13.4.17
- Next.js: Unauthenticated Remote Code Execution in Image Optimization API when SVG files are usedcritical · GHSA-2464-fhr4-w9xw
- Next.js: Unauthenticated Remote Code Execution in Image Optimization API when AVIF files are usedcritical · GHSA-2xp9-vwfh-vxw4
- Next.js has a Middleware / Proxy bypass in Pages Router applications using i18nhigh · GHSA-36qx-fr4f-26g5
Upgrading to 15.5.29 clears them.
Release by release
- New
Tracing: Add opt-in flag to send a subset of development traces to url
- Fixed
next/image: Empty blur image when animated #54028
- Fixed
Do not output pages 404 in tree view if app not-found is used
- Fixed
Fix scroll bailout logic when targeting fixed/sticky elements
- New
8 other lines we could not sort, mostly version bumps
- 13.4.17
Debug tracing: add updated modules and page to HMR span
- 13.4.17
Upgrade edge-runtime dependency
- 13.4.17
Refactor layout router creation in app-render
- 13.4.17
OpenTel: Remove the internal (ipc) fetched from traces in a non-verbose mode
- 13.4.17
cleanup: Remove unnecessary effect dep
- 13.4.17
Next build: use exported
handle_issuesfrom turbopack - 13.4.17
node-web-streams: Remove tee shim, use ReadableStream.tee
- 13.4.17
Revert "fix(47299): allow testing pages with metadata in jsdom test environment"
10 internal lines (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.