Releases: opennextjs/opennextjs-cloudflare
@opennextjs/cloudflare@1.19.1
Patch Changes
- #1189
236ce14Thanks @fatihy101! - fix(tag-cache): forwardisStale()inwithFilter
@opennextjs/cloudflare@1.19.0
Minor Changes
-
#1168
9a26846Thanks @conico974! - Add support for SWR (stale-while-revalidate) inrevalidateTagSee the AWS implementation for more details.
Patch Changes
-
#1184
c7d6425Thanks @vicb! - fix for Next.js CVE-2026-23869See the CVE-2026-23869 summary for details.
This CVE is fixed by bumping the minium Next.js release version to 15.5.15/16.2.3
-
#1177
e814a63Thanks @conico974! - Fixuse cachenot working as expected in Next 16+
@opennextjs/cloudflare@1.18.1
Patch Changes
-
#1176
2232651Thanks @conico974! - fix for OG with Next 16.2.2 -
#1166
f89fba1Thanks @ash1day! - fix: sort.endsWith()checks by path length descending to prevent suffix collisions in dynamic requiresRoutes whose paths are suffixes of other routes (e.g.
/test/appvs/) were resolved incorrectly because the shorter path matched first in the generated.endsWith()chain. Sorting by path length descending ensures more specific (longer) paths are always checked first.Fixes #1156.
@opennextjs/cloudflare@1.18.0
Minor Changes
-
#1159
75f5f0aThanks @edmundhung! - Use remote dev for R2 cache populationUsing remote dev is not subject to the Cloudflare API rate limit of 1,200 requests per 5 minutes that caused failures for large applications with thousands of prerendered pages.
@opennextjs/cloudflare@1.17.3
Patch Changes
-
#1160
161e726Thanks @matthewvolk! - fix(patches): includeprefetch-hints.jsonin loadManifest build-time inliningNext.js 16.2.0 introduced
prefetch-hints.jsonas a new server manifest loaded unconditionally
byNextNodeServer.getPrefetchHints(). The file exists in the build output but wasn't matched by
the glob pattern*-manifest.json, causing the patchedloadManifest()to throw at runtime.
@opennextjs/cloudflare@1.17.2
Patch Changes
-
#1151
a143282Thanks @nathanschram! - fix: handle known optional manifests gracefully in loadManifest/evalManifest patchesNext.js loads certain manifests with
handleMissing: true(returning{}when the file doesn't
exist). The adapter's build-time glob scan doesn't find these files when they're conditionally
generated, so the patched function threw at runtime, crashing dynamic routes with 500.Instead of a blanket catch-all, handle only the specific optional manifests from Next.js
route-module.ts:react-loadable-manifest(Turbopack per-route, not all routes have dynamic imports)subresource-integrity-manifest(only whenexperimental.sriconfigured)server-reference-manifest(App Router only)dynamic-css-manifest(Pages Router + Webpack only)fallback-build-manifest(only for/_errorpage)prefetch-hints(new in Next.js 16.2)_client-reference-manifest.js(optional for static metadata routes, evalManifest)
Manifest matching strips
.jsonbefore comparison since some Next.js constants omit
the extension (SUBRESOURCE_INTEGRITY_MANIFEST,DYNAMIC_CSS_MANIFEST, etc.).Unknown manifests still throw to surface genuine errors.
Fixes #1141.
@opennextjs/cloudflare@1.17.1
@opennextjs/cloudflare@1.17.0
Minor Changes
- #1133
25d5835Thanks @dario-piotrowicz! - Update themigratecommand to attempt to create an R2 bucket for caching, if that is not possible an application without caching enabled will be generated instead.
@opennextjs/cloudflare@1.16.6
Patch Changes
- #1138
4487f1fThanks @james-elicx! - Fix the CLI potentially setting a future compatibility date in the wrangler config when workerd has published a version matching a future date, by capping to the current date.
@opennextjs/cloudflare@1.16.5
Patch Changes
-
#1127
2b437f1Thanks @dario-piotrowicz! - In themigratecommand, add an initial step to create a Next.js config file (required by open-next) if it doesn't exist -
#1126
8c3a36eThanks @alex-all3dp! - fix: prevent Worker hang on HEAD requests to static assets