next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 15.0.2 to 15.0.3
1 release in betweenevery note read
Security
41 advisories still affect 15.0.3
- 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
Stitch errors with react owner stack
- New
Enable owner stack in experimental build
- New
Add experiment for sharpjs cpu flags
- New
Add test for fetch with auth in use cache
- New
30 other lines we could not sort, mostly version bumps
- 15.0.3
Read page name from work store in server module map proxy
- 15.0.3
codemod: Should not transform when param is not used
- 15.0.3
Complete refactor to prerender
- 15.0.3
next-codemod(upgrade): optional catch when missing dev script
- 15.0.3
Warn on sync access if dynamicIO is not enabled
- 15.0.3
Update data access error and documentation
- 15.0.3
Test cached form action with revalidate
- 15.0.3
Remove the bottom collapse button in dev overlay
- 15.0.3
Unify cache filling and lazy-module warming
- 15.0.3
Replace
turbopack://[project]/...sourcemap uris withfile://...in development
39 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.