Upgrade Next.js and compatible dependencies - #17
Merged
Merged
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
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
@next/env, andeslint-config-nextto 16.3.0.unstable_retryto the stableretryAPI.Why
This adopts the supported Next.js 16.3 APIs, keeps the workspace current within its declared version ranges, and resolves compatibility and typing changes at their source. The dependency refresh also reduces the audit result from 23 advisories to one moderate advisory in Drizzle Kit's development-only dependency chain.
Validation
pnpm install --frozen-lockfilepnpm outdated --compatible --recursive— no remaining compatible updatespnpm peers checkpnpm verify— 26/26 tasks and 461 tests passedgit diff --check