- 26 Jan, 2026 2 commits
-
-
vercel-release-bot authored
-
Hendrik Liebau authored
-
- 11 Dec, 2025 6 commits
-
-
vercel-release-bot authored
-
Hendrik Liebau authored
facebook/react#35351 Co-authored-by:Josh Story <story@hey.com>
-
vercel-release-bot authored
-
Hendrik Liebau authored
Co-authored-by:Josh Story <story@hey.com>
-
Josh Story authored
-
Zack Tanner authored
* remove urlencoded server action handling (#14) * remove urlencoded server action handling * urlencoded POSTs should still flow through action handler * bailout early for urlencoded * tweak handling to 404 in feetch action case * error when there are no server actions (#15) * remove custom error * remove dev gate * error when there are no server actions * gate against dev * Check whether action ids are valid before parsing (#16) * Check whether action ids are valid before parsing In an effort to narrow access to parsing methods Next.js now prequalifies MPA form parsing by ensuring there are only valid action IDs as part of the submission. This is not meant to be a strong line of defense against malicious payloads since action IDs are not private and are for many apps relatively easy to acquire. It does however provide some limited narrowing of code paths so that action decoding only happens for plausible actions Additionally all other branches that use next-action header now consistently check the header before proceeding with parsing. This is also a perf improvement. * fix test assertion --------- Co-authored-by:
Zack Tanner <1939140+ztanner@users.noreply.github.com> * test fix --------- Co-authored-by:
Josh Story <story@hey.com>
-
- 03 Dec, 2025 5 commits
-
-
vercel-release-bot authored
-
JJ Kasper authored
-
JJ Kasper authored
-
Josh Story authored
* Update React Version Update React Version * Disable some tests that fail spuriously. Should improve test coverage of otherwise blocked tests * types are wrong
-
JJ Kasper authored
-
- 03 Jul, 2025 4 commits
-
-
vercel-release-bot authored
-
Zack Tanner authored
Backports: - #81263
-
Zack Tanner authored
Backports: - #80734
-
Zack Tanner authored
Backports: - #80884 Co-authored-by:Niklas Mischkulnig <4586894+mischnic@users.noreply.github.com>
-
- 18 Jun, 2025 3 commits
-
-
Benjamin Woodruff authored
Backports https://github.com/vercel/next.js/pull/78184 (@timneutkens) User request: (https://vercel.slack.com/archives/C06CUNEC64D/p1750069211569019) > could the change from `next internal turbo-trace-server` to `next internal trace` be backported to a non-canary Next.js version? (to align with the published docs suggestion) > > currently, the docs say "You can interpret the file using `next internal trace [path-to-file]`:" ... and then further down "On versions where `trace` is not available, the command was named `turbo-trace-server`" ... which means that anyone on non-canary versions following the docs right now will receive `error: unknown command 'trace'` > > https://nextjs.org/docs/app/guides/local-development#turbopack-tracing The `mdx` change here isn't really relevant, since we don't build docs from this branch, but it merges cleanly, so it's harmless. Co-authored-by:
Tim Neutkens <tim@timneutkens.nl>
-
vercel-release-bot authored
-
Jiachi Liu authored
-
- 16 Jun, 2025 1 commit
-
-
Jiachi Liu authored
-
- 29 May, 2025 4 commits
-
-
vercel-release-bot authored
-
Jude Gao authored
-
Jude Gao authored
Since the corresponding change has been released in Vercel CLI, we can re-enable the test.
-
Jude Gao authored
Reverts vercel/next.js#77797 Reinstate the `Vary` header to prevent browsers from incorrectly reusing RSC responses during bfcache restores.
-
- 23 May, 2025 3 commits
-
-
Donny/강동윤 authored
### What? Add tests for the interestingness detection for the RC
-
Donny/강동윤 authored
### What? Fix the usefulness detector for the React Compiler ### Why? JSX was also a target of the React Compiler
-
Benjamin Woodruff authored
Without this, some files may fail to open correctly. Internal discussion: https://vercel.slack.com/archives/C07UWUAF95Z/p1747261772629689
-
- 19 May, 2025 1 commit
-
-
Hendrik Liebau authored
Backport of #79309 to 15.3.x
-
- 06 May, 2025 7 commits
-
-
vercel-release-bot authored
-
Benjamin Woodruff authored
This is a straightforward backport of https://github.com/vercel/next.js/pull/78488. There were only a few minor merge conficts. This *mostly* impacted use of Turbopack with persistent caching (which is canary-gated), but we saw some reports of it without persistent caching, so this backports the fix. Tested with ``` cargo check cargo test -p turbo-tasks-backend cargo test -p turbo-tasks-memory ```
-
JJ Kasper authored
Backport of #78261 to 15.3.x Co-authored-by:Will Binns-Smith <wbinnssmith@gmail.com>
-
JJ Kasper authored
Backport of #78874 to 15.3.x Co-authored-by:Donny/강동윤 <kdy1997.dev@gmail.com>
-
Donny/강동윤 authored
https://github.com/vercel/next.js/pull/78453 is a bugfix for sourcemap on windows
-
JJ Kasper authored
Backport of #77963 to 15.3.x Co-authored-by:Jiachi Liu <inbox@huozhi.im>
-
JJ Kasper authored
Backport of #78325 to 15.3.x
-
- 17 Apr, 2025 2 commits
-
-
vercel-release-bot authored
-
Jiachi Liu authored
-
- 16 Apr, 2025 1 commit
-
-
Donny/강동윤 authored
### What? Backport https://github.com/vercel/next.js/pull/75605 ### Why? x-ref: https://vercel.slack.com/archives/C06DGJ420TZ/p1744644426250019
-
- 15 Apr, 2025 1 commit
-
-
Steven authored
Backport of https://github.com/vercel/next.js/pull/78149 to 15.3.x
-