Version Packages #1058
Merged
Version Packages #1058
Conversation
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
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
3377421 to
68c2b8a
Compare
vicb
approved these changes
Dec 11, 2025
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/[email protected]
Patch Changes
#1061
2fb99000aaca974c7847d7a53d1621e08b58b820Thanks @vicb! - Bump Next and React to fix vulnerabilities (CVE-2025-55184 and CVE-2025-55183)Note that Next 13 has been removed from the allowed peer Dependency range,
because it is vulnerable under specific conditions.
If possible we will check the conditions at build time and relax the peer dependency.
See https://react.dev/blog/2025/12/11/denial-of-service-and-source-code-exposure-in-react-server-components
See https://nextjs.org/blog/security-update-2025-12-11
#1055
85128a5b7e68fc3ddd155eca5ade59a5c5b2a8b2Thanks @guerra-eb! - fix: AWS ApiGW v1 (REST) converter incorrectly parses all query parameters as arrays[email protected]
Patch Changes
2fb99000aaca974c7847d7a53d1621e08b58b820,85128a5b7e68fc3ddd155eca5ade59a5c5b2a8b2]: