Merged
Conversation
gpbl
changed the title
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.
Summary
version-nextv10 upgrade page that still mirrored the old v9 migration guidenavLayout="after"default and recommend auditing copied wrappers after upgradingWhy
PR #2903 had useful migration ideas, but most of its website/versioning plumbing has already landed separately on
main.This extracts the still-relevant migration guidance into a smaller patch that matches the current docs structure.
Impact
Developers reading the
nextdocs now get a real v9-to-v10 migration path instead of a page that still describes v9-era deprecations as upcoming.Validation
pnpm buildpnpm exec prettier --check website/versioned_docs/version-next/upgrading.mdx