- 25 Jul, 2026 1 commit
-
-
next-js-bot[bot] authored
-
- 24 Jul, 2026 1 commit
-
-
Luke Sandberg authored
## Summary A minimal mitigation for the TypeScript 7 problem on the `15.5.x` line, ported from the `next-16-2` mitigation (#95837). TypeScript 7's native compiler no longer ships the JavaScript compiler API (`typescript/lib/typescript.js`) that Next.js loads via `require('typescript')`, so an installed TS7 produces surprising failures with no actionable message. This was reported against 16.2 in #95801. ## What it does - Because the missing compiler-API file makes an installed TS7 look like a *missing* dependency, `hasNecessaryDependencies` now also exposes the resolved `typescript/package.json` path. `verifyTypeScriptSetup` reads that version up front and, if it's `>= 7.0.0` (including prereleases — `7.0.0-beta`/`-rc`, nightly `7.0.0-dev.*`, via the `7.0.0-0` sentinel with `includePrerelease`), throws a `CompileError` with guidance to install TypeScript 6 or upgrade Next.js, before the `require()` runs. Unlike the 16.2 mitigation, no install-specifier change is needed here: the `15.5` line already pins TypeScript auto-installs via `getTypeScriptPackageSpec` (`typescript@5.8.2`) rather than pulling `latest`. Applies to both `next dev` and `next build`. ## Notes - This is the minimal fix for `15.5`; the full `experimental.useTypeScriptCli` backend (real TS7 support) is a separate, larger effort and was considered overkill for this stable line. - Related: `next-16-2` mitigation #95837, and full backport #95831. ## Verification - `pnpm --filter=next build` - Boundary verified against the compiled semver: `5.8.2` / `6.x` (incl. `6.0.0-beta`) are not rejected; `7.0.0-dev.*` / `7.0.0-beta` / `7.0.0-rc` / `7.0.0` / `7.0.2` are rejected. - Manual repro with `typescript@7` + `next@15.5`: `next build` and `CI=1 next build` exit non-zero with the actionable error instead of the opaque failure.
-
- 21 Jul, 2026 10 commits
-
-
next-js-bot[bot] authored
-
Sebastian "Sebbie" Silbermann authored
https://github.com/vercel/next-js-mirror/pull/129Co-authored-by:
Karim Rahal <karim.rahal@vercel.com>
-
Sebastian "Sebbie" Silbermann authored
https://github.com/vercel/next-js-mirror/pull/127Co-authored-by:
Karim Rahal <karim.rahal@vercel.com>
-
Sebastian "Sebbie" Silbermann authored
https://github.com/vercel/next-js-mirror/pull/123Co-authored-by:
Steven <steven@ceriously.com>
-
-
- 16 Jul, 2026 1 commit
-
-
Sebastian "Sebbie" Silbermann authored
-
- 01 Jul, 2026 2 commits
-
-
next-js-bot[bot] authored
-
next-js-bot[bot] authored
-
- 30 Jun, 2026 1 commit
-
-
Sebastian "Sebbie" Silbermann authored
Co-authored-by:Steven <steven@ceriously.com>
-
- 17 Jun, 2026 2 commits
-
-
Jiwon Choi authored
### Why? Stacked replacement for #94844. This is the top PR in the `next-15-5` backport stack and is based on #94847. This was discovered while investigating the fork PR CI failure on #94829. Fork PRs to `next-15-5` do not receive `secrets.TURBO_TOKEN`, but the pinned `ijjk/rust-cache` action throws when `TURBO_TOKEN` is missing. Canary no longer uses that action for these Rust cache paths; it starts the local `sccache` action and only configures Vercel Artifacts when a token is available. This ports the fork-safe cache behavior from canary without taking the broader native-builder and workflow rewrites from the source PRs. Source PRs / ported parts: - #91873: add the local `.github/actions/sccache` action and move Rust workflows off `ijjk/rust-cache`. - #92911: install `cargo-binstall` and use the `vercel/sccache` cargo-binstall path. - #93164: keep the Vercel Artifacts token/team wiring used by canary. - #94319: remove the remaining `build_and_deploy.yml` `ijjk/rust-cache` step. ### How? - Add the canary `.github/actions/sccache` action and install `cargo-binstall` from `setup-rust`. - Replace the remaining `ijjk/rust-cache` usage in reusable Rust workflows with the local `sccache` action. - Remove the remaining `build_and_deploy.yml` rust-cache step so fork PRs do not load the token-requiring external action. <!-- NEXT_JS_LLM_PR -->
-
Jiwon Choi authored
### Why? Backports https://github.com/vercel/next.js/pull/86863 to `next-15-5` so the skip-trailing-slash-redirect fixture rewrites to the assigned custom domain instead of the protected deployment-specific URL. ### How? - Cherry-picked `551b32d8` with `-x`. - Updates `test/e2e/skip-trailing-slash-redirect/app/middleware.js` to use `https://middleware-external-rewrite-target.vercel.app`. ### Verification - `pnpm build` passed. (`pnpm build-all` is not available on `next-15-5`.) - Not run: `pnpm test-start test/e2e/skip-trailing-slash-redirect/index.test.ts` (stopped per follow-up request to just cherry-pick and open PR). - Not run: `pnpm test-start-turbo test/e2e/skip-trailing-slash-redirect/index.test.ts` (stopped per follow-up request to just cherry-pick and open PR). <!-- NEXT_JS_LLM_PR --> Co-authored-by:
Hendrik Liebau <mail@hendrik-liebau.de>
-
- 10 Jun, 2026 1 commit
-
-
Sebastian "Sebbie" Silbermann authored
Backports https://github.com/vercel/next.js/pull/93302
-
- 09 Jun, 2026 1 commit
-
-
Sebastian "Sebbie" Silbermann authored
-
- 03 Jun, 2026 2 commits
-
-
Sebastian "Sebbie" Silbermann authored
Co-authored-by:
Matt Mastracci <matthew@mastracci.com> Co-authored-by:
dagecko <cnyhuis@vigilantnow.com> Co-authored-by:
Benjamin Woodruff <github@benjam.info> Co-authored-by:
Benjamin Woodruff <benjamin.woodruff@vercel.com>
-
Sebastian "Sebbie" Silbermann authored
Backports https://github.com/vercel/next.js/pull/94302 15.x still receives bug fixes so we need to maintain the release workflow. Even if it's just for perf, the less differences, the easier it is to find causes of divergent behavior.
-
- 01 Jun, 2026 3 commits
-
-
Sebastian "Sebbie" Silbermann authored
-
Sebastian "Sebbie" Silbermann authored
-
Sebastian "Sebbie" Silbermann authored
Backports: 1. #86157 The other fixes are due to tests using unpinned versions. The latest versions (e.g. Tailwind or `eslint-config-next`) are no longer compatible with Node.js 18 (used in Next.js 15 CI). --------- Co-authored-by:
Hendrik Liebau <mail@hendrik-liebau.de> Co-authored-by:
Claude Opus 4.7 (1M context) <noreply@anthropic.com>
-
- 07 May, 2026 7 commits
-
-
Sebastian "Sebbie" Silbermann authored
-
Sebastian "Sebbie" Silbermann authored
Co-authored-by:Matt Mastracci <matthew@mastracci.com>
-
Sebastian "Sebbie" Silbermann authored
-
Tim Neutkens authored
Applies https://github.com/vercel/next.js/commit/d166096c399c4fc4e09cd2d1bf26dca6579a855d for canary and handles the Turbopack-side implementation for `middleware-manifest.json` which is used for edge runtime middleware.ts --------- Co-authored-by:
Zack Tanner <1939140+ztanner@users.noreply.github.com>
-
Tim Neutkens authored
## What? The Turbopack path incorrectly included a double backslash instead of one backslash in the regex matcher.
-
Sebastian "Sebbie" Silbermann authored
Co-authored-by:
Niklas Mischkulnig <4586894+mischnic@users.noreply.github.com> Co-authored-by:
Tobias Koppers <tobias.koppers@googlemail.com>
-
Sebastian "Sebbie" Silbermann authored
-
- 06 May, 2026 8 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
-