- 31 Aug, 2026 3 commits
-
-
next-js-bot[bot] authored
-
Sebastian "Sebbie" Silbermann authored
Since 15.x supports a Node.js version not supported by a secure sharp version, we have to conditionally block AVIF optimization based on the used libheif version. I added a test that runs for each support major sharp version to validate only the fixed version optimizes AVIF.
-
Sebastian "Sebbie" Silbermann authored
This addresses the deploy test failures from the v15.5.24 deploy run attempts (https://github.com/vercel/next.js/actions/runs/32871018966). This PR only updates assertions. Backporting the relevant fixes is out of scope. Assertion fixes: - `no-server-actions`: backports the #87279 portion for the MPA test. The multipart POST was sent without a boundary parameter, which Vercel answers with a 405 before the request reaches the Next.js server; with `boundary=test` the deployed app returns the expected 404 with the `x-nextjs-action-not-found` header. - `actions-unrecognized`: the JS-disabled form submission with an unrecognized action id used to log a 500 on the server while Vercel returned a 405 to the client; current 15.5.x deployments return the 500 itself. The deploy branch now asserts the 500 with an updated FIXME. Canary fixed the underlying runtime 500 in c2a10f111d by responding 404 - `metadata`: prerendered metadata routes are served on Vercel as static files with the platform default `max-age=0, must-revalidate` instead of the immutable cache header from the prerender manifest. The icons test expects that in deploy mode, with a FIXME noting the expectations unify once #83215 is backported. - `middleware-general`: the nodejs middleware function bundle does not include the project package.json when deployed, so `/test-node-fs` fails with ENOENT (`open /var/task/package.json`, confirmed in function logs). The test asserts the 500 in deploy mode behind a FIXME. Deploy skips, each due to deploy-mode flakiness or unsupported infra: - The whole `test/e2e/app-dir/segment-cache/` directory: timeouts and `act()` prefetch-response mismatches move between suites from run to run against the identical published package. The suite is testing an experimental feature so coverage on an LTS release is less relevant. - `sub-shell-generation`: applies canary's own gate from #91353 - `app-static` force-static revalidation: already carries a TODO about a suspected ISR bug; now also skipped in deploy mode, referencing that TODO. `server-actions-redirect-middleware-rewrite` is a legit bug caused by https://github.com/vercel/next.js/pull/96011. `app-custom-routes` is broken due to bot challenges. Filed a ticket that hopefully resolves that issue: https://vercel.slack.com/archives/C02K2HCH5V4/p1788175011380479
-
- 28 Aug, 2026 2 commits
-
-
Sebastian "Sebbie" Silbermann authored
-
Niklas Mischkulnig authored
Backport https://github.com/vercel/next.js/pull/97792
-
- 25 Aug, 2026 4 commits
-
-
next-js-bot[bot] authored
-
Sebastian "Sebbie" Silbermann authored
https://github.com/vercel/next-js-mirror/pull/164Co-authored-by:
Steven <steven@ceriously.com>
-
- 24 Aug, 2026 1 commit
-
-
Sebastian "Sebbie" Silbermann authored
Co-authored-by:Jiwon Choi <devjiwonchoi@gmail.com>
-
- 20 Aug, 2026 1 commit
-
-
Sebastian "Sebbie" Silbermann authored
-
- 17 Aug, 2026 1 commit
-
-
Sebastian "Sebbie" Silbermann authored
Backports https://github.com/vercel/next.js/pull/96919
🤖 Generated with [Claude Code](https://claude.com/claude-code)
-
- 14 Aug, 2026 28 commits
-
-
Sebastian "Sebbie" Silbermann authored
Backports #96895 to `next-15-5`, adapted to this branch's layout (a single `test-deploy` job, no adapter jobs). This branch had a bug where `test-deploy` resolved `NEXT_TEST_VERSION` as `github.event.inputs.nextVersion || 'canary'`, so release runs always installed `canary` and ignored the released version.
-
next-js-bot[bot] authored
-
Sebastian "Sebbie" Silbermann authored
-
next-js-bot[bot] authored
-
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. -
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>
-
-
Sebastian "Sebbie" Silbermann authored
-
next-js-bot[bot] authored
-
next-js-bot[bot] authored
-
Sebastian "Sebbie" Silbermann authored
Co-authored-by:Steven <steven@ceriously.com>
-
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>
-
Sebastian "Sebbie" Silbermann authored
Backports https://github.com/vercel/next.js/pull/93302
-
Sebastian "Sebbie" Silbermann authored
-
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.
-
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>
-