1. 07 May, 2026 6 commits
  2. 06 May, 2026 14 commits
  3. 05 May, 2026 2 commits
  4. 27 Apr, 2026 6 commits
  5. 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
  6. 22 Apr, 2026 2 commits
  7. 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
  8. 15 Apr, 2026 4 commits