Next.js Daily: Route Matching Fixes and React Upgrades

Transcript

Good morning, this is Next.js Daily for March 7th, 2026.

Andrew Clark merged a fix for route matching where the algorithm incorrectly fell back to catch-all routes when static child subtrees didn't match. This resolves cases where `/dashboard/settings/profile` would incorrectly match `/dashboard/[...catchall]` instead of the intended static route.

Jonas Herrmannsdörfer addressed server action redirects in multi-zone deployments. Previously, calling `redirect()` in a server action would produce blank pages when targeting different Next.js zones. The fix adds build ID validation to trigger proper full-page navigation when needed.

Jude Gao introduced standardized evaluation frameworks for Next.js, creating a unified system where `pnpm eval` runs both baseline and agent-assisted tests to measure documentation effectiveness on AI behavior.

Zack Tanner re-introduced partial fallback route upgrading, allowing pages to upgrade from partial fallbacks to full route shells when dynamic parameters become available. This feature was previously reverted but returns with proper infrastructure support.

The Next.js bot upgraded React dependencies from version `3bc2d414` to `46103596`, updating 62 files across the compiled React DOM packages.

Additional improvements include Hendrik Liebau's runtime data caching for partially static pages during initial loads, and fixes to Turbopack's alias resolution where query parameters were being dropped during module resolution.

JJ Kasper expanded documentation for deploy test custom scripts, while Tim Neutkens updated adapter documentation with missing fields and implementation details.

What's next: The team continues focusing on routing stability and performance optimizations. Documentation improvements are expanding to cover more deployment scenarios.

That's your Next.js update for today. We'll be back tomorrow with more development news.