1. 06 Aug, 2026 1 commit
  2. 31 Jul, 2026 1 commit
  3. 25 Jul, 2026 1 commit
  4. 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
  5. 21 Jul, 2026 10 commits
  6. 16 Jul, 2026 1 commit
  7. 01 Jul, 2026 2 commits
  8. 30 Jun, 2026 1 commit
  9. 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
  10. 10 Jun, 2026 1 commit
  11. 09 Jun, 2026 1 commit
  12. 03 Jun, 2026 2 commits
  13. 01 Jun, 2026 3 commits
  14. 07 May, 2026 7 commits
  15. 06 May, 2026 6 commits