-
Notifications
You must be signed in to change notification settings - Fork 30.2k
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: vercel/next.js
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v15.4.8
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: vercel/next.js
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v15.4.10
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 7 commits
- 83 files changed
- 5 contributors
Commits on Dec 10, 2025
-
Configuration menu - View commit details
-
Copy full SHA for bd84546 - Browse repository at this point
Copy the full SHA bd84546View commit details
Commits on Dec 11, 2025
-
Backport Next.js changes to v15.4.9 (#24)
* 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 <[email protected]> --------- Co-authored-by: Josh Story <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for d0edaac - Browse repository at this point
Copy the full SHA d0edaacView commit details -
Configuration menu - View commit details
-
Copy full SHA for 2ff781e - Browse repository at this point
Copy the full SHA 2ff781eView commit details -
Co-authored-by: Josh Story <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 596f513 - Browse repository at this point
Copy the full SHA 596f513View commit details -
Configuration menu - View commit details
-
Copy full SHA for d1449e5 - Browse repository at this point
Copy the full SHA d1449e5View commit details -
Backport facebook/react#35351 for 15.4.9 (#87087)
facebook/react#35351 Co-authored-by: Josh Story <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 6129673 - Browse repository at this point
Copy the full SHA 6129673View commit details -
Configuration menu - View commit details
-
Copy full SHA for 43cb546 - Browse repository at this point
Copy the full SHA 43cb546View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v15.4.8...v15.4.10