1. 14 Oct, 2026 4 commits
  2. 12 Oct, 2026 1 commit
  3. 06 Oct, 2026 1 commit
  4. 30 Sep, 2026 4 commits
  5. 25 Sep, 2026 1 commit
  6. 24 Sep, 2026 1 commit
    • Sebastian "Sebbie" Silbermann's avatar
      [lts-maintenance][test] Adjust deploy assertions for platform drift and the edge… · 812ae7db
      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: 's avatarClaude Code (kimi-k3[1m]) <noreply@anthropic.com>
      812ae7db
  7. 22 Sep, 2026 2 commits
  8. 01 Sep, 2026 1 commit
  9. 31 Aug, 2026 3 commits
    • next-js-bot[bot]'s avatar
      v15.5.25 · 013ee1d2
      next-js-bot[bot] authored
      013ee1d2
    • Sebastian "Sebbie" Silbermann's avatar
      [15.5.x] Re-enable AVIF image optimization with a runtime libheif version guard (#97954) · d64c0d1e
      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.
      d64c0d1e
    • Sebastian "Sebbie" Silbermann's avatar
      [test] Fix 15.5.x deploy tests (#97977) · 7f6b4007
      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
      7f6b4007
  10. 28 Aug, 2026 2 commits
  11. 25 Aug, 2026 4 commits
  12. 24 Aug, 2026 1 commit
  13. 20 Aug, 2026 1 commit
  14. 17 Aug, 2026 1 commit
  15. 14 Aug, 2026 13 commits