@opennextjs/aws

cli: honor --dangerously-use-unsupported-next-version when passed as standalone

keep supporting a Next.js major version until the second next major is released

Allow up to six rendering attempts when falling through fallback: false routes, matching the Next.js router server (since Next.js 13.4.13). A sixth matching route candidate previously returned a 500.

keep the runtime alive until fetch cache entries are written on Next.js 15.4+

Fix pages with fallback: false returning a 404 instead of falling through to a less specific dynamic route on Next.js 16.4.

request headers deleted by the middleware are no longer forwarded

Apply every matching beforeFiles rewrite in order so Next.js-generated

compile the routing matcher regular expressions only once

percent-encode query values when rebuilding the query string, so values containing "&", "=", "+" or "%" reach Next.js intact

Await background work registered while a detached promise runner is draining.

Apply patchBackgroundRevalidation to the compiled Next.js runtimes

Resolve the request store each time the @next/request-context getter is called, instead of capturing the store of the request that last published it

cache: support scoped response cache keys in fixed Next.js releases

Only serve cached responses for GET and HEAD requests in the cache interceptor

Make the SQS revalidation queue non-blocking via waitUntil

Provide waitUntil from the AWS streaming wrappers

Register the composable cache handler at the top-level cacheHandlers config key for Next.js 16

scope the composable cache's pending writes to the request, not the isolate

Pass process.env explicitly when spawning the Next.js build

quote cache interceptor ETag values so they are valid HTTP entity-tags

e2e: AVIF was renabled for optimization in Next 16.3.4

Improve status code handling in cacheInterceptor

use getSetCookie() to preserve multiple Set-Cookie headers in middleware

Forward images.dangerouslyAllowLocalIP to fetchExternalImage on Next.js 16 instead of hardcoding false, so external images served from hosts resolving to private IPs (e.g. an internal media proxy) can be optimized again when the user has explicitly opted out of the SSRF guard in their Next.js config.

Stop the cache interceptor from serving cached 404 and 500 responses with a cacheable cache-control.

Persist runtime cache tag associations for App Router APP_PAGE entries when using original-mode tag caches, including pages generated on demand and tags added after the build.

Fix server/instrumentation.js does not exist build failure on Next.js 16

Fix for undefined rsc data in the cache