- 11 Dec, 2025 3 commits
-
-
vercel-release-bot authored
-
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> * fix test --------- Co-authored-by:
Josh Story <story@hey.com>
-
- 10 Dec, 2025 2 commits
- 23 Sep, 2025 2 commits
-
-
vercel-release-bot authored
-
Zack Tanner authored
Backports: - #80734 Fixes #82801
-
- 18 Aug, 2025 2 commits
-
-
vercel-release-bot authored
-
Zack Tanner authored
Backports: - #82588 Co-authored-by:JJ Kasper <jj@jjsweb.site>
-
- 30 Jul, 2025 2 commits
-
-
vercel-release-bot authored
-
Zack Tanner authored
Backports: - #82118 --------- Co-authored-by:Steven <steven@ceriously.com>
-
- 29 Jul, 2025 1 commit
-
-
Zack Tanner authored
Backports: - #82114 Co-authored-by:Steven <steven@ceriously.com>
-
- 12 Jun, 2025 1 commit
-
-
vercel-release-bot authored
-
- 11 Jun, 2025 1 commit
-
-
Zack Tanner authored
Backports: - #76880 - #77044 - #77053 - #77395 - #77414
-
- 20 May, 2025 2 commits
-
-
vercel-release-bot authored
-
JJ Kasper authored
This backports https://github.com/vercel/next.js/pull/79386 to 14 release channel
-
- 08 Apr, 2025 2 commits
-
-
vercel-release-bot authored
-
Zack Tanner authored
The previous [backport](https://github.com/vercel/next.js/pull/77794) caused an issue due to how imports are resolved on canary vs v14, resulting in a message about using node.js APIs in middleware. This moves the import to the `web` directory and adds a test case for the warning. Closes NDX-1014
-
- 07 Apr, 2025 1 commit
-
-
vercel-release-bot authored
-
- 04 Apr, 2025 1 commit
-
-
Zack Tanner authored
Backports: - #64923
-
- 24 Mar, 2025 2 commits
-
-
vercel-release-bot authored
-
JJ Kasper authored
Backports https://github.com/vercel/next.js/pull/77474 to v14
-
- 17 Mar, 2025 2 commits
-
-
vercel-release-bot authored
-
JJ Kasper authored
Backports https://github.com/vercel/next.js/pull/77201 to v14 release branch
-
- 11 Feb, 2025 1 commit
-
-
vercel-release-bot authored
-
- 10 Feb, 2025 4 commits
-
-
Zack Tanner authored
-
Zack Tanner authored
Backports: - #75766
-
Zack Tanner authored
Backports: - #75561 - #73482 --------- Co-authored-by:JJ Kasper <jj@jjsweb.site>
-
Jiachi Liu authored
-
- 07 Jan, 2025 3 commits
-
-
vercel-release-bot authored
-
Janka Uryga authored
Fixes #74062 (`jotai` ran into this error [when they added `"type": "commonjs"` to their package.json](https://github.com/pmndrs/jotai/discussions/2579#discussioncomment-9812492)) > this is a bug in the transform we do when a `'use client'` directive is encountered. I think what's happening is that we're creating a virtual file that uses ESM import/export syntax, but it's called proxy.js (not proxy.mjs), so the `"type": "commonjs" `makes turbopack "correctly" upset at the ESM syntax. https://github.com/vercel/next.js/issues/74062#issuecomment-2555922867 The (slightly kludgy) solution is to use `proxy.mjs` or `proxy.cjs` to force the module format, bypassing the issue where `proxy.js` changes meaning depending on `package.json#type`.
-
JJ Kasper authored
This backports https://github.com/vercel/next.js/pull/74164 to leverage built-in waitUntil if available instead of using the approach that keeps the stream open until the waitUntil promise resolves. x-ref: [slack thread](https://vercel.slack.com/archives/C02K2HCH5V4/p1736211642221149?thread_ts=1734707275.666089&cid=C02K2HCH5V4)
-
- 03 Jan, 2025 1 commit
-
-
Steven authored
Backports PR https://github.com/vercel/next.js/pull/74257 to 14.x
-
- 26 Dec, 2024 1 commit
-
-
vercel-release-bot authored
-
- 24 Dec, 2024 2 commits
-
-
Zack Tanner authored
Backports: - #71564 - #74154 --------- Co-authored-by:JJ Kasper <jj@jjsweb.site>
-
Zack Tanner authored
Backports: - #73900 Co-authored-by:Hendrik Liebau <mail@hendrik-liebau.de>
-
- 19 Dec, 2024 2 commits
-
-
vercel-release-bot authored
-
Zack Tanner authored
Updates React from 14898b6a9 to 178c267a4e. ### React upstream changes - https://github.com/facebook/react/pull/31842 - https://github.com/facebook/react/pull/31841
-
- 13 Dec, 2024 2 commits
-
-
Steven authored
Backport https://github.com/vercel/next.js/pull/73925 to 14.x
-
Steven authored
Backport https://github.com/vercel/next.js/pull/73923 to 14.x
-