diff --git a/.changeset/cache-interception-error-cache-control.md b/.changeset/cache-interception-error-cache-control.md
deleted file mode 100644
index 7860efc5c..000000000
--- a/.changeset/cache-interception-error-cache-control.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-"@opennextjs/aws": patch
----
-
-Stop the cache interceptor from serving cached 404 and 500 responses with a cacheable `cache-control`.
-
-`notFound()` results on ISR routes are written to the incremental cache by Next.js, and the interceptor served them with the entry's own `cache-control` — up to `s-maxage=31536000` for a route that declares no `revalidate`. A transient 404 could therefore be held at the CDN for a year. The interceptor now applies the same override the server path already applies in `OpenNextNodeResponse.fixHeadersForError`, which it was bypassing by returning a result directly. As on the server path, only 404 and 500 are overridden, and `OPEN_NEXT_DANGEROUSLY_SET_ERROR_HEADERS=true` opts out.
diff --git a/.changeset/forward-dangerously-allow-local-ip.md b/.changeset/forward-dangerously-allow-local-ip.md
deleted file mode 100644
index d7a4d6cb2..000000000
--- a/.changeset/forward-dangerously-allow-local-ip.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"@opennextjs/aws": patch
----
-
-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.
diff --git a/examples/app-pages-router/CHANGELOG.md b/examples/app-pages-router/CHANGELOG.md
index b5261d9f1..bdc263422 100644
--- a/examples/app-pages-router/CHANGELOG.md
+++ b/examples/app-pages-router/CHANGELOG.md
@@ -1,5 +1,12 @@
 # app-pages-router
 
+## 0.1.66
+
+### Patch Changes
+
+- Updated dependencies [[`dd6ea23dfdc84c54c7d27950794faf67b4d930f1`](https://github.com/opennextjs/opennextjs-aws/commit/dd6ea23dfdc84c54c7d27950794faf67b4d930f1), [`78ca8fe40d80fbe950e8478fc3400d40614e195d`](https://github.com/opennextjs/opennextjs-aws/commit/78ca8fe40d80fbe950e8478fc3400d40614e195d)]:
+  - @opennextjs/aws@4.1.2
+
 ## 0.1.65
 
 ### Patch Changes
diff --git a/examples/app-pages-router/package.json b/examples/app-pages-router/package.json
index e13faddc3..70a106239 100644
--- a/examples/app-pages-router/package.json
+++ b/examples/app-pages-router/package.json
@@ -1,6 +1,6 @@
 {
   "name": "app-pages-router",
-  "version": "0.1.65",
+  "version": "0.1.66",
   "private": true,
   "scripts": {
     "openbuild": "node ../../packages/open-next/dist/index.js build --build-command \"npx turbo build\"",
diff --git a/packages/open-next/CHANGELOG.md b/packages/open-next/CHANGELOG.md
index 8a5c1ca63..30884b21b 100644
--- a/packages/open-next/CHANGELOG.md
+++ b/packages/open-next/CHANGELOG.md
@@ -1,5 +1,15 @@
 # open-next
 
+## 4.1.2
+
+### Patch Changes
+
+- [#1227](https://github.com/opennextjs/opennextjs-aws/pull/1227) [`dd6ea23dfdc84c54c7d27950794faf67b4d930f1`](https://github.com/opennextjs/opennextjs-aws/commit/dd6ea23dfdc84c54c7d27950794faf67b4d930f1) Thanks [@vicb](https://github.com/vicb)! - Stop the cache interceptor from serving cached 404 and 500 responses with a cacheable `cache-control`.
+
+  `notFound()` results on ISR routes are written to the incremental cache by Next.js, and the interceptor served them with the entry's own `cache-control` — up to `s-maxage=31536000` for a route that declares no `revalidate`. A transient 404 could therefore be held at the CDN for a year. The interceptor now applies the same override the server path already applies in `OpenNextNodeResponse.fixHeadersForError`, which it was bypassing by returning a result directly. As on the server path, only 404 and 500 are overridden, and `OPEN_NEXT_DANGEROUSLY_SET_ERROR_HEADERS=true` opts out.
+
+- [#1226](https://github.com/opennextjs/opennextjs-aws/pull/1226) [`78ca8fe40d80fbe950e8478fc3400d40614e195d`](https://github.com/opennextjs/opennextjs-aws/commit/78ca8fe40d80fbe950e8478fc3400d40614e195d) Thanks [@lcordier42](https://github.com/lcordier42)! - 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.
+
 ## 4.1.1
 
 ### Patch Changes
diff --git a/packages/open-next/package.json b/packages/open-next/package.json
index ab6836e00..c3410beb2 100644
--- a/packages/open-next/package.json
+++ b/packages/open-next/package.json
@@ -3,7 +3,7 @@
     "access": "public"
   },
   "name": "@opennextjs/aws",
-  "version": "4.1.1",
+  "version": "4.1.2",
   "bin": {
     "open-next": "./dist/index.js"
   },