1. 25 Jul, 2026 1 commit
  2. 24 Jul, 2026 1 commit
    • Luke Sandberg's avatar
      [15.5] Reject TypeScript >= 7.0 with an actionable error (#96110) · fcc0424b
      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.
      fcc0424b
  3. 21 Jul, 2026 10 commits
  4. 16 Jul, 2026 1 commit
  5. 01 Jul, 2026 2 commits
  6. 30 Jun, 2026 1 commit
  7. 17 Jun, 2026 2 commits
    • Jiwon Choi's avatar
      [15.5.x][ci] Port sccache fallback from #91873/#92911/#93164/#94319 (#94848) · c8f9fcb5
      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 -->
      c8f9fcb5
    • Jiwon Choi's avatar
      [backport] [test] Fix external rewrite target URL origin (#94829) · 019fcca5
      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: 's avatarHendrik Liebau <mail@hendrik-liebau.de>
      019fcca5
  8. 10 Jun, 2026 1 commit
  9. 09 Jun, 2026 1 commit
  10. 03 Jun, 2026 2 commits
  11. 01 Jun, 2026 3 commits
  12. 07 May, 2026 7 commits
  13. 06 May, 2026 8 commits
    • Sebastian "Sebbie" Silbermann's avatar
      v15.5.16 · ad6fd4e5
      Sebastian "Sebbie" Silbermann authored
      ad6fd4e5
    • JJ Kasper's avatar
      Ignore malformed CSP nonce headers (#103) · 79d7dff1
      JJ Kasper authored
      79d7dff1
    • JJ Kasper's avatar
      router-server: guard upgrade proxy against absolute-url SSRF (#77) (#102) · c4f69086
      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)
      c4f69086
    • JJ Kasper's avatar
      Fix i18n middleware matching for default-locale data routes (#82) (#100) · 6c72e0b4
      JJ Kasper authored
      * Fix i18n middleware matching for default-locale data routes
      
      * unskip node middleware on deploy
      6c72e0b4
    • Zack Tanner's avatar
      fix: add explicit checks for RSC header (#83) (#99) · 3e247110
      Zack Tanner authored
      (cherry picked from commit 807e363b13cc9395aa74f75122d1d16b4a46dc1a)
      3e247110
    • Zack Tanner's avatar
      fix proxy matching for segment prefetch URLs (#89) (#97) · 25926510
      Zack Tanner authored
      * fix: proxy should match segment prefetches for canonical urls
      
      * include .rsc handling
      25926510
    • Josh Story's avatar
      Strip next-resume header from incoming requests (#93) · 73de0458
      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.
      73de0458
    • Josh Story's avatar
      Escape properties for beforeInteractive scripts (15.5) (#87) · 086dfa7f
      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
      086dfa7f