Version Packages - #1228
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 27, 2026 05:17
056b443 to
f7e92a9
Compare
commit: |
Contributor
Author
Coverage Report
File CoverageNo changed files found. |
vicb
approved these changes
Aug 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@opennextjs/aws@4.1.2
Patch Changes
#1227
dd6ea23dfdc84c54c7d27950794faf67b4d930f1Thanks @vicb! - Stop the cache interceptor from serving cached 404 and 500 responses with a cacheablecache-control.notFound()results on ISR routes are written to the incremental cache by Next.js, and the interceptor served them with the entry's owncache-control— up tos-maxage=31536000for a route that declares norevalidate. 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 inOpenNextNodeResponse.fixHeadersForError, which it was bypassing by returning a result directly. As on the server path, only 404 and 500 are overridden, andOPEN_NEXT_DANGEROUSLY_SET_ERROR_HEADERS=trueopts out.#1226
78ca8fe40d80fbe950e8478fc3400d40614e195dThanks @lcordier42! - Forwardimages.dangerouslyAllowLocalIPtofetchExternalImageon Next.js 16 instead of hardcodingfalse, 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.app-pages-router@0.1.66
Patch Changes
dd6ea23dfdc84c54c7d27950794faf67b4d930f1,78ca8fe40d80fbe950e8478fc3400d40614e195d]: