[lts-maintenance][test] Adjust deploy assertions for platform drift and the edge…
[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>
Showing
Please
register
or
sign in
to comment