Releases: opennextjs/opennextjs-aws
Releases · opennextjs/opennextjs-aws
v3.10.4
v3.10.3
Changes
- #1145
1e19ae2f5427c56d882c6393a1cdd77c6a5a4a0fThanks @314systems! - fix: exclude unsupported Next.js 16 releases from peer dependencies. - #1148
4836a91e2e04b5e168b66c1f84c8679f777a913dThanks @vicb! - DefineglobalThis.nextVersionglobally
v3.10.2
Changes
- #1142
d7286a305477f7c967ae9c34ff9d2c63ee782dc0- Fix cache interceptor isStale handling for Next 16+ - #1140
ae93c945788ba2c92d8a2b74b537b5ba917aee72Thanks @vicb! - fix(ci): pin npm@11.5.1 to fix pre-release workflow - #1139
4bdfd292f985913f3298eb3f30a7790b877e0464Thanks @vicb! -applyRuledoes not require afixfield - #1144
1b5a6595dd0226e4bedcf34f8c7a4b3f37621063- Deprecate NEXT_BUILD_ID env variable, and replace it with OPEN_NEXT_BUILD_ID
v3.10.1
Changes
- #1137
4db87785105bf1fe4fbb344ca76dd9ea83b084cdThanks @vicb! - fix for Next.js CVE-2026-23869
v3.10.0
Changes
- #1122
1a75cc712c56448f5d77abb810cf4af259802a28- Add support for SWR (stale-while-revalidate) inrevalidateTag - #1121
fad4632ef4278db0a040b3a3948d259c1cf43c05Thanks @ntltd! - Fix ISR revalidation to also accept valid Next.js non-200 status codes (307, 308 and 404) - #1135
323448b83f6c292398338f9d6307c113d1246da9Thanks @ktKongTong! - fix: handle multiple same-name headers as array in fetch proxyExternalRequest - #1132
8210035cc30720702a6052e22bbf9275ef54c636- add support for prefetch inlining in the cache interceptor - #1117
3a2b1b9497c531e9f07f66f7a140f152a9d8fc26Thanks @clichedmoog! - Auto-filter non-Linux platform-specific native binaries (e.g. @swc/core-darwin-arm64) from Lambda bundles during traced files copy - #1118
e49782af723ec97f1373e654a7e400e1ba3e827eThanks @tsurumeso! - Preserve query parameters during i18n redirects to a localized path - #1125
92f1f300341321a820e60133eb9ee399b39fc5d1Thanks @rikublock! - fix: dereference symlinks when copying public folder
v3.9.16
Changes
- #1107
0344a7d8c7872e50186e4676748861082f7b85a8- Fix for setting PPR data - #1114
88c2944775874145a541b25b0fffe2cae5c598cdThanks @dario-piotrowicz! - FixfindNextConfigreturning the incorrect result and also expend the return result to be an object with both the path and a new flag indicating whether the file is in TypeScript or not
v3.9.15
Changes
- #1104
5f3f7e78fc90f4fc8cddfab1bd51bef0908a6f07Thanks @anonrig! - Fix EACCES errors when building with read-only node_modules
v3.9.14
Changes
- #1098
43d31b798791de11f844eedec6c2e7943e92e2bbThanks @vicb! - EmptyNextNodeServer#handleNextImageRequestto avoid pulling unneeded deps
v3.9.13
Changes
- #1095
9f6b673e0e5ac7804dd82c11b9adc30654043b6aThanks @dario-piotrowicz! - Implement newfindNextConfigfunction to find the project's Next.js config file if present - #1094
bb0bcea33832fa9663057181efb68daf467fe35fThanks @vicb! - Check for supported Next version - #1097
44e67e4ba51b501dc95bc18711d61223f3eca9d8Thanks @vicb! - bump Next and React version for CVE-2026-23864
v3.9.12
Changes
- #1091
2c47a92e097e31082420410d9c4034f94b229323Thanks @vicb! - fix the detection of the runtime (webpack vs turbopack)