chore(deps): upgrade Next.js to 16.3 - #209
Draft
ericyangpan wants to merge 2 commits into
Draft
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What changed
Why
This keeps the framework and deployment adapter aligned while preserving a reproducible lockfile and current validation snapshot.
Impact
Application behavior is unchanged. The build and deployment toolchain now uses Next.js 16.3 and the corresponding OpenNext patch release.
Validation
pnpm install --frozen-lockfilepnpm test:ci— 177 passed, 4 skippedpnpm type-checkpnpm validate:i18npnpm data-health:check— 0 issuespnpm formatpnpm biomepnpm spellLocal validation used Node 24.14.0; the repository declares Node 22.