1. 06 May, 2026 14 commits
  2. 05 May, 2026 2 commits
  3. 27 Apr, 2026 6 commits
  4. 24 Apr, 2026 2 commits
    • Zack Tanner's avatar
      [ci]: switch to GitHub runners (#93164) · 70defda2
      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
      70defda2
    • Zack Tanner's avatar
      Fix invalid HTML response for route-level RSC requests in deployment adapter (#91541) · af0e96ba
      Zack Tanner authored
      In a deployed environment, `onCacheEntryV2` determines whether a
      postponed response is HTML-origin or RSC-origin by checking whether
      meta.url ends with `.rsc`.
      
      For some dynamic full-route RSC requests, Next was passing a URL with
      query params into onCacheEntry, for example:
      `/[tenant]/samples.rsc?nxtPtenant=tenant-x`
      
      Because that string does not end with .rsc, `onCacheEntryV2`
      misclassified the request as HTML and treated it as text/html instead of
      an RSC response.
      
      This PR normalizes the URL before passing it to `onCacheEntry`, so the
      callback receives the pathname rather than the full URL-with-query.
      
      ---------
      Co-authored-by: 's avatarJJ Kasper <jj@jjsweb.site>
      af0e96ba
  5. 22 Apr, 2026 2 commits
  6. 21 Apr, 2026 4 commits
    • JJ Kasper's avatar
      Patch setHeader for direct route handlers (#93101) · 6fd09bf8
      JJ Kasper authored
      ## Summary
      - apply the `setHeader` cookie-support patch to direct route module
      handlers in `prepare()`
      - make `patchSetHeaderWithCookieSupport()` idempotent so both entry
      paths can call it safely
      - add an adapter-like direct RSC regression test that fails without the
      patch
      
      Closes: NEXT-4919
      
      ## Testing
      - `NEXT_SKIP_ISOLATE=1 NEXT_TEST_MODE=start pnpm testheadless
      test/e2e/app-dir/cache-components/cache-components.test.ts -t "should
      ignore late setHeader calls for direct RSC handlers after headers are
      sent"`
      
      <!-- NEXT_JS_LLM_PR -->
      6fd09bf8
    • Zack Tanner's avatar
      Strengthen _rsc cache-busting param (#92755) · 688ed31e
      Zack Tanner authored
      This updates `_rsc` cache-busting param generation to use a stronger
      digest so different RSC request variants are much less likely to produce
      the same value.
      
      It also updates the related request-validation and injected
      resume/instant-test paths so they continue to generate and validate the
      same `_rsc` values across client, server, and edge-reachable codepaths.
      688ed31e
    • Steven's avatar
      fix(next/image): ensure `images.maximumResponseBody` applies to local images too (#92920) · 62ef3050
      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.
      62ef3050
    • JJ Kasper's avatar
      Ensure x-nextjs-data header is only set during resolve (#92752) · 15341fdf
      JJ Kasper authored
      Makes sure we set this header during route resolving so user request
      doesn't need to.
      15341fdf
  7. 15 Apr, 2026 6 commits
    • nextjs-bot's avatar
      v16.2.4 · 2275bd85
      nextjs-bot authored
      2275bd85
    • Andrew Imm's avatar
    • Tobias Koppers's avatar
      Turbopack: shorter error message for ModuleBatchesGraph::get_entry_index (#92828) · 8a540b58
      Tobias Koppers authored
      ### What?
      
      In `ModuleBatchesGraph::get_entry_index`, when an entry module is not
      found in the graph, the error message included the full list of all
      possible entries (with their resolved string identifiers). This is an
      expensive operation that requires async resolution of every entry's
      `ident().to_string()`.
      
      ### Why?
      
      In production builds, this verbose error output is unnecessary overhead
      and produces very long error messages that are hard to read. The list of
      possible entries is only useful during development/debugging.
      
      ### How?
      
      Gate the expensive "possible entries" diagnostic behind
      `cfg!(debug_assertions)`. In release builds, a short `bail!("Entry is
      not in graph")` is used instead. In debug builds, the full diagnostic
      with all possible entry identifiers is still shown to aid debugging.
      
      This mirrors the same approach already applied to
      `ChunkGroupInfo::get_index_of`.
      
      <!-- NEXT_JS_LLM_PR -->
      8a540b58
    • Niklas Mischkulnig's avatar
    • Tobias Koppers's avatar
      turbo-tasks: Fix recomputation loop by allowing cell cleanup on error during recomputation (#92725) · 2ad9d3fb
      Tobias Koppers authored
      ### What?
      
      Fix an infinite recomputation loop in turbo-tasks by allowing cell
      cleanup to proceed during recomputation even when the task result is an
      error.
      
      ### Why?
      
      When a task errors during normal execution, cell cleanup is
      intentionally skipped. The rationale is that errors during normal
      execution are often transient eventual-consistency issues caused by
      reading stale inputs — keeping old cell data prevents "cell no longer
      exists" errors for dependent tasks that are reading those cells.
      
      However, during **recomputation** (a task re-executing without being
      marked dirty), nothing about its inputs has changed. Any error it
      produces is therefore not transient. If cell cleanup is skipped in this
      case, stale cells remain in place, which trigger further recomputations,
      which produce further errors, which skip further cleanups — creating an
      infinite loop.
      
      ### How?
      
      - Detect whether a task execution is a recomputation by checking
      `task.is_dirty().is_none()` at completion time (a recomputing task was
      not dirty when it started executing).
      - Propagate `is_recomputation` through
      `TaskExecutionCompletePrepareResult` to both
      `task_execution_completed_prepare` and
      `task_execution_completed_cleanup`.
      - In both places where cell cleanup is gated on `result.is_ok()` /
      `!is_error`, extend the condition to also allow cleanup when
      `is_recomputation` is true.
      
      This ensures that stale cells produced by a erroring recomputation are
      cleaned up, breaking the infinite loop.
      
      <!-- NEXT_JS_LLM_PR -->
      Co-authored-by: 's avatarClaude Opus 4.6 (1M context) <noreply@anthropic.com>
      2ad9d3fb
    • Andrew Imm's avatar
      Compiler: Support boolean and number primtives in next.config defines (#92731) · 6f3808e2
      Andrew Imm authored
      Expand `config.compiler.define` to support number and boolean primitives
      as well.
      
      The support is already in Turbopack's rewrite engine, as well as
      Webpack's DefinePlugin. We just need to modify the zod schema to
      actually support passing numbers and bools.
      
      Added an E2E test that should check all supported types.
      6f3808e2
  8. 14 Apr, 2026 1 commit
    • Luke Sandberg's avatar
      Scope Safari ?ts= cache-buster to CSS/font assets only (Pages Router) (#92580) · fbc7684e
      Luke Sandberg authored
      ### What?
      
      Refactors the Safari `?ts=` cache-busting workaround in the Pages Router so it **only appears on CSS and font URLs**, not on script tags or script preload links.
      
      ### Why?
      
      The `?ts=` timestamp was originally added to all preloaded assets as a workaround for a [Safari caching bug](https://bugs.webkit.org/show_bug.cgi?id=187726) (see [#5860](https://github.com/vercel/next.js/issues/5860)). When it appears on `<script>` tags, the Turbopack runtime's `getAssetSuffixFromScriptSrc()` reads the executing script's query string and infers it as the `ASSET_SUFFIX`, which then leaks onto all static asset URLs — including images. This causes `next/image` validation errors because the image URL gets an unexpected `?ts=` parameter.
      
      Fixes #92118
      
      ### How?
      
      Instead of maintaining parallel `assetQueryString` (with `?ts=`) and `scriptAssetQueryString` (without `?ts=`) paths, this PR:
      
      1. **`assetQueryString`** carries only the deployment token (`?dpl=...`) and is used for all script-related URLs (script tags, script preloads)
      2. **`safariCacheBuster`** is a new, separate field (`?ts=<timestamp>` or `""`) that is only combined with `assetQueryString` at the 3 CSS/font URL sites via a `joinQueryStrings()` helper
      3. Removes the `scriptAssetQueryString` / `scriptMutableAssetQueryString` / `cssAssetQueryString` fields entirely
      
      The Safari cache-buster is computed the same way as before (dev server only, Safari user-agent check) — it just no longer contaminates the base query string.
      
      ### Test plan
      
      - [x] Updated existing test in `test/e2e/app-document/rendering.test.ts` to assert `?ts=` appears only on `<link rel="preload" as="style">` and `<link rel="preload" as="font">`, and does NOT appear on `<script>` or `<link rel="preload" as="script">`
      - [x] `pnpm --filter=next types` passes
      
      <!-- NEXT_JS_LLM_PR -->
      fbc7684e
  9. 13 Apr, 2026 2 commits
    • Luke Sandberg's avatar
      Turbopack: fix filesystem watcher config not applying follow_symlinks(false) (#92631) · 805d758d
      Luke Sandberg authored
      ## Summary
      
      - The notify `Config` uses a builder pattern where `with_follow_symlinks()` consumes `self` and returns a new `Config`, but the return value was being discarded — so `follow_symlinks` remained at its default (`true`).
      - The `RecommendedWatcher` branch was also passing `Config::default()` instead of the configured `config` object, ignoring the config entirely.
      
      ## Test plan
      
      - [x] `cargo check -p turbo-tasks-fs` passes
      - Behavioral: symlinks under the watched root will now trigger events for the symlink itself rather than the target, matching the intent of the existing comment.
      
      <!-- NEXT_JS_LLM_PR -->
      805d758d
    • Evan Yu's avatar
      chore: Bump reqwest to 0.13.2 (#92713) · 1056fae3
      Evan Yu authored
      Fixes #91653
      
      Running `next dev` with the latest Turbopack fails to fetch fonts on
      Windows ARM machines, resulting in an `http2 feature is not enabled`
      error. This issue was fixed in `reqwest` v0.13.2:
      https://github.com/seanmonstar/reqwest/pull/2927
      1056fae3
  10. 08 Apr, 2026 1 commit