- 14 Oct, 2026 4 commits
-
-
next-js-bot[bot] authored
-
Sebastian Sebbie Silbermann authored
-
Sebastian "Sebbie" Silbermann authored
-
Sebastian "Sebbie" Silbermann authored
Co-authored-by:
Hendrik Liebau <mail@hendrik-liebau.de> Co-authored-by:
Claude Code (kimi-k3[1m]) <noreply@anthropic.com>
-
- 12 Oct, 2026 1 commit
-
-
Sebastian "Sebbie" Silbermann authored
Backports https://github.com/vercel/next.js/pull/99896 to `releases/lts/maintenance`. Conflict resolution against the 15.5 test variants: kept the branch's `#_next-gtm`/`#_next-ga` selectors and `elementsByCss` script-count assertions, and replaced `waitFor(1000)` with the deterministic `retry` on `window.google_tag_manager` (mirroring what the original did in the pages test). <!-- NEXT_JS_LLM --> Co-authored-by:
Benjamin Woodruff <benjamin.woodruff@vercel.com>
-
- 06 Oct, 2026 1 commit
-
-
Sebastian "Sebbie" Silbermann authored
Backports https://github.com/vercel/next.js/pull/99323 ## test plan - [x] [test_e2e_deploy_release run](https://github.com/vercel/next.js/actions/runs/36347199201) Co-authored-by:
Claude Code (kimi-k3[1m]) <noreply@anthropic.com>
-
- 30 Sep, 2026 4 commits
-
-
next-js-bot[bot] authored
-
Josh Story authored
-
Josh Story authored
-
Sebastian "Sebbie" Silbermann authored
Co-authored-by:David Ilie <david@davidilie.com>
-
- 25 Sep, 2026 1 commit
-
-
Sebastian "Sebbie" Silbermann authored
Backports https://github.com/vercel/next.js/pull/93400 to `next-15-5`. The `create-draft-prs` and `update-prs` jobs fail on every 15.5.x release deploy run because `secrets.GH_UPDATE_NEXT_WORKFLOW_TRIGGER` no longer resolves (e.g. https://github.com/vercel/next.js/actions/runs/35759438119). The cherry-pick conflicted with the diverged 15.5 workflow; the resolution deletes both job blocks, which are the last jobs in the file and have no remaining dependents. <!-- NEXT_JS_LLM --> Co-authored-by:
Claude Code (kimi-k3[1m]) <noreply@anthropic.com>
-
- 24 Sep, 2026 1 commit
-
-
Sebastian "Sebbie" Silbermann authored
[lts-maintenance][test] Adjust deploy assertions for platform drift and the edge redirect regression (#99094) Forks three deploy-mode assertions so the 15.5.x release deploy suite documents current behavior and turns red when it changes, instead of skipping the tests or asserting stale behavior. Analysis of the failing v15.5.26 run: https://github.com/vercel/next.js/actions/runs/35759438119 (failures reproduced against the still-live deployment URLs from the job logs). `test/e2e/image-optimizer/sharp.test.ts`: Vercel's image CDN now passes AVIF input through unmodified regardless of the Accept header (byte-identical passthrough verified against the failing run's live deployment for WebP-only, Chrome, and old-Safari accept shapes). Deployments assert the passthrough, matching the local pipeline's vulnerable-libheif branch. Per the shared image optimizer suite's `skipDeployment` rationale this is the platform's own behavior, so the comment states it factually rather than as a FIXME. `test/e2e/og-api/index.test.ts`: a middleware-returned `ImageResponse` responds 200 with `content-type: image/png` but an empty body on 15.5.x deployments, while the same ImageResponse works in an edge app route of the same deployment and 16.x deployments pass. Deploy mode asserts the empty body behind a FIXME pending platform/adapter investigation. Not new in 15.5.26. Already reproduces in 15.5.25: https://github.com/vercel/next.js/actions/runs/33433813993 Fails with ``` [Error: Unsupported OpenType signature $] ``` -- https://vercel.com/vtest314-next-e2e-tests/vtest314-e2e-tests/H9k7NE3evCdjUmdKCfdfWruDAnY1/logs?selectedLogId=m88pk-1790190085395-eb2bdc5dc1ac&panelState=opened `test/e2e/app-dir/server-actions-redirect-middleware-rewrite`: real regression from the #96011 backport (3eaa59f0). `createRedirectRenderResult` in `packages/next/src/server/app-render/action-handler.ts` requires the `initURL` request meta, which the 15.5.x edge-function path never sets, so the action POST returns 500 on Vercel (verified against the live deployment: edge returns 500, node returns 303). Canary sets `initURL` in `route-module.ts` since #88831. Deploy mode clicks the button and asserts the action POST's 500 response behind a FIXME until the runtime fix is backported. Co-authored-by:
Claude Code (kimi-k3[1m]) <noreply@anthropic.com>
-
- 22 Sep, 2026 2 commits
-
-
next-js-bot[bot] authored
-
-
- 01 Sep, 2026 1 commit
-
-
Sebastian "Sebbie" Silbermann authored
Backports https://github.com/vercel/next.js/pull/89036/changes#diff-cf635dd531d3fcad56634e5dec0bc4974b226005935e1a42370d5518ed9ee687R526 The `HEADER` method will cause Vercel to treat these tests as originating from bots causing challenges in later tests. Fixes https://github.com/vercel/next.js/actions/runs/33433813993/job/99643438429#step:35:377 ## test plan - [x] [deploy test passes on this branch](https://github.com/vercel/next.js/actions/runs/33496592051/job/99840891680?pr=98132)
-
- 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 13 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>
-