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@3.4.1
Patch Changes
#708
7eda030388880d8ad25d3f4692e24bac31b7ec4f
Thanks @sommeeeer! - fix: add early return for downplayed aws-sdk errorsIn the logger adapter:
An issue was identified where downplayed errors from the aws-sdk client (f.ex NoSuchKey from S3) would not return from the function early. This caused unnecessary invocation of
console.error
outside the conditional.#704
e5678b39e0f3c21d3e30d08a89f5cb0acdd3d050
Thanks @dario-piotrowicz! - fix: make sure edge function entries are properly awaited#702
1981a47dd3dbc77066d2bf5cad5d5d406fecb010
Thanks @vicb! - refactor(cache): deprecate global disableDynamoDBCache and disableIncrementalCacheIn the cache adapter:
globalThis.disableDynamoDBCache
is deprecated and will be removed.use
globalThis.openNextConfig.dangerous?.disableTagCache
instead.globalThis.disableIncrementalCache
is deprecated and will be removed.use
globalThis.openNextConfig.dangerous?.disableIncrementalCache
instead.#709
b4ad0f0e0f6069ca87f3b72c23d655cedebc86e5
Thanks @conico974! - fix: stableIncrementalCache is only used for Next.js >= 14.1app-pages-router@0.1.6
Patch Changes
7eda030388880d8ad25d3f4692e24bac31b7ec4f
,e5678b39e0f3c21d3e30d08a89f5cb0acdd3d050
,1981a47dd3dbc77066d2bf5cad5d5d406fecb010
,b4ad0f0e0f6069ca87f3b72c23d655cedebc86e5
]:app-router@0.1.6
Patch Changes
7eda030388880d8ad25d3f4692e24bac31b7ec4f
,e5678b39e0f3c21d3e30d08a89f5cb0acdd3d050
,1981a47dd3dbc77066d2bf5cad5d5d406fecb010
,b4ad0f0e0f6069ca87f3b72c23d655cedebc86e5
]: