- 06 May, 2026 10 commits
-
-
Sebastian "Sebbie" Silbermann authored
-
JJ Kasper authored
-
JJ Kasper authored
* test: add rewrite request smuggling coverage * router-server: guard upgrade proxy against absolute-url SSRF * test: relax rewrite smuggling socket timeout * router-server: preserve local websocket upgrades (cherry picked from commit 846b7f825db2205c79e48b6fdc4acd8908235a43)
-
JJ Kasper authored
* Fix i18n middleware matching for default-locale data routes * unskip node middleware on deploy
-
Zack Tanner authored
(cherry picked from commit 807e363b13cc9395aa74f75122d1d16b4a46dc1a)
-
Zack Tanner authored
* fix: proxy should match segment prefetches for canonical urls * include .rsc handling
-
Josh Story authored
This header is used by proxies to perform a concatenating resume render for partial prerendering. It is never sent from the client so we can filter it out when running in a mode that does not have an intermediate proxy.
-
Josh Story authored
* Escape properties for beforeInteractive scripts props set on a next/script with beforeInteractive are serialized as JSON into an inline script to be exectuted prior to hydration by Next.js. The props were not additionally escaped and if user input was rendered as through a script it could allow fro XSS. This has alwways been true if you pass user input into the script body or via dangerouslySetInnHTML however and it is always the developers responsibility to sanitize user input before rendering. However wherever React has some automatic escaping to act as an additional defense against common mistakes leading to vulnerabilities like XSS Next.js should mirror that becasue from the user's perspective it is not clear that React is not directly rendering the script props and content. This change adds additional escaping so that serialized properties cannot break out of the script scope and execute unexpected payloads. * Move htmlescape to shared/lib we have auditing that server files aren't included in client chunks but the new htmlescape usage in next/script is causing that validation to fail. This refactors the utility into lib/shared
-
Zack Tanner authored
* fix: skip internal param normalization in unsupported environments (#79) * add isWrappedByNextServer flag
-
Sebastian "Sebbie" Silbermann authored
-
- 27 Apr, 2026 6 commits
-
-
Benjamin Woodruff authored
`pnpm dlx` isn't using a lockfile. Using the self-contained binary from GitHub and validate the checksum lets us effectively pin `datadog-ci` and all of its possible transitive dependencies. This is a follow-up for https://vercel.slack.com/archives/C0APPN2LC83/p1775073127894859 (cherry picked from commit 631fae95)
-
Zack Tanner authored
Switch CI from self-hosted runners to GitHub-hosted runners and fix the follow-up issues that showed up once the hosted jobs were exercised. - Move Linux workflows onto `ubuntu-latest-16-core-oss`, Windows workflows onto `windows-latest-8-core-oss`, and the native mac release lane onto `macos-15-intel`. - Update the reusable build workflow to work in hosted environments by relying on `runner.os` instead of label string matching, and by removing the hardcoded `/home/runner` `fnm` path. - Make Turbo/sccache configuration explicit for hosted runners: - unify on `vtest314-next-adapter-e2e-tests` - pass `TURBO_TOKEN` via workflow env/secrets instead of assuming runner-level env - switch Turbo cache mode to `local:rw,remote:rw` so jobs still have local cache behavior when remote cache is unavailable - Update the `sccache` action defaults/docs to use the hosted-runner secret setup (`TURBO_TOKEN`) instead of the old self-hosted token wiring. - Make Datadog reporting fail open so missing `DATA_DOG_API_KEY` does not block CI. - Fix the CLI reserved-port test so it asserts Next’s own `-p 1` validation instead of failing earlier on hosted Linux due to privileged-port binding. - Replace the live `musl.cc` dependency in `native-builder.Dockerfile` with musl sysroots imported from GHCR-hosted `rust-musl-cross` images, keeping the existing `/opt/*-cross` layout used by the Linux native build scripts. - Fix the macOS native build workaround s so it applies to all *-apple-darwin targets based on the Cargo target OS rather than the host architecture, which avoids napi-build injecting the unsupported -Wl linker arg when @next/swc is linked with rust-lld on hosted mac runners. Test Plan: - This PR's CI - This [build_and_deploy](https://github.com/vercel/next.js/actions/runs/24865715983/job/72801225722) job running on every arch (cherry picked from commit 70defda2)
-
Zack Tanner authored
Stacked on https://github.com/vercel/next.js/pull/93245 Commit signing is required for anything that lands on `canary`. Our previous workflow of using a PAT to push a commit no longer works, since that would have been an unsigned commit. In #93245 we switched to an app token for release workflow steps. This continues by: - Telling Lerna to bump packages but not commit - Creating a signed commit with the staged changes via GitHub's API - Then running the publish flow Test Plan: Dry run [here](https://github.com/vercel/next.js/actions/runs/25001287978/job/73211826479) Commit [here](https://github.com/vercel/next.js/commit/3a8456a62b56615e2f8c1d1e6e7b4e14ce89e078) (cherry picked from commit 012fd7df)
-
Zack Tanner authored
Moves all release workflows off of a GH PAT and uses an app with a short-lived token instead. Test Plan: Dry run [here](https://github.com/vercel/next.js/actions/runs/24934593874). However, this workflow is blocked until we figure out commit signing for the bot app. Some options: - The bot account generates a signing key and we use it in CI (not great, bypasses the app) - The org bypasses signature verification for the bot user (also not great, requires an exemption rule) - We need to rework the commit step so Lerna does not do the push, and instead trigger it via the app + GH API. This seems like the best option, will be added in a follow-up PR. Note: `create-release-branch` workflow is broken in its current form, as we will not be restoring administrator privileges to adjust environment settings. This will become a manual step in the future. (cherry picked from commit e69de2ff)
-
Zack Tanner authored
Moves the `environment` into `publishRelease` rather than `trigger_release` since the actual action we want to create environment rules for is the publish step. (cherry picked from commit 2b846de4)
-
Zack Tanner authored
Switches from a long-lived token to trusted publishing OIDC flow. This requires a bump to Node (for feature support). Otherwise just dropping unnecessary envs. (cherry picked from commit 129896c2)
-
- 22 Apr, 2026 1 commit
-
-
JJ Kasper authored
x-ref: #92755 --------- Co-authored-by:Zack Tanner <1939140+ztanner@users.noreply.github.com>
-
- 21 Apr, 2026 3 commits
-
-
JJ Kasper authored
## Summary - pin the shared test harness and affected TypeScript tests to `typescript@5.8.2` - pin Next.js TypeScript auto-install paths to `typescript@5.8.2` so missing deps do not resolve to v6 - lock the first-time TypeScript test fixture to the same exact version ## Testing - `pnpm exec tsc -v` - `pnpm why typescript --depth 0` - `pnpm types:test-lib` *(still fails on existing declaration/type surface errors, but no longer fails on the TS6 `moduleResolution=node10` deprecation)*
-
Steven authored
In a previous PR https://github.com/vercel/next.js/pull/88183, we added `images.maximumResponseBody` but in only applied to external images. This PR ensures the same config also applies to internal images.
-
JJ Kasper authored
Makes sure we set this header during route resolving so user request doesn't need to.
-
- 08 Apr, 2026 2 commits
-
-
nextjs-bot authored
-
Sebastian "Sebbie" Silbermann authored
* Avoid consuming cyclic models multiple times * [react-sync] Allow locking in manual sync
-
- 01 Apr, 2026 1 commit
-
-
Benjamin Woodruff authored
-
- 19 Mar, 2026 2 commits
-
-
nextjs-bot authored
-
Zack Tanner authored
Backports: - #89963 --------- Co-authored-by:Steven <steven@ceriously.com>
-
- 18 Mar, 2026 1 commit
-
-
JJ Kasper authored
Backport: Fix(pages-router): restore Content-Length and ETag for /_next/data/ JSON responses (#90304) (#91615) Backports #90304 Co-authored-by:Henry <lllomh@qq.com>
-
- 16 Mar, 2026 2 commits
-
-
nextjs-bot authored
-
Zack Tanner authored
* fix: patch http-proxy to prevent request smuggling in rewrites (#65) * namespace temp files (#50) * fix: patch http-proxy to prevent request smuggling in rewrites * ncc (cherry picked from commit e9a0b6dd0a27d07c0526b1d8d1b71c13ad4951dd) * block hop-by-hop TE rewrite smuggling bypass (#70) * block hop-by-hop TE rewrite smuggling bypass * more hardening * chore: minimize lockfile delta for http-proxy patch
-
- 04 Feb, 2026 2 commits
-
-
nextjs-bot authored
-
JJ Kasper authored
-
- 30 Jan, 2026 1 commit
-
-
Niklas Mischkulnig authored
Co-authored-by:
Jimmy Lai <laijimmy0@gmail.com> Co-authored-by:
Claude Opus 4.5 <noreply@anthropic.com> Co-authored-by:
JJ Kasper <jj@jjsweb.site>
-
- 28 Jan, 2026 9 commits
-
-
JJ Kasper authored
-
nextjs-bot authored
-
JJ Kasper authored
Full run here https://github.com/vercel/next.js/actions/runs/21455905546/job/61796583243
-
Zack Tanner authored
Backports: - #85529 Co-authored-by:Tim Neutkens <tim@timneutkens.nl>
-
Zack Tanner authored
Backports: - #89040 Co-authored-by:Tim Neutkens <tim@timneutkens.nl>
-
Niklas Mischkulnig authored
-
Niklas Mischkulnig authored
-
Niklas Mischkulnig authored
-
Niklas Mischkulnig authored
-