docs: split Upgrades off the Versionierung page - #3064
Open
mfal wants to merge 4 commits into
Open
Conversation
The page already covers upgrading (codemod CLI, migration guide links, deprecation warnings) beyond just semver rules. Update its title/navTitle and the three cross-reference link texts pointing at it accordingly. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Contributor
Coverage Report for ./packages/components/
File CoverageNo changed files found. |
This reverts commit 46259c5.
Contributor
🚀 Preview DeploymentPreview environments are ready:
Images:
|
The versioning page mixed two concerns: the semver contract (what's guaranteed, lifecycle status) and the upgrade workflow (migration guides, the codemod CLI, deprecation warnings, the post-release npm version-mismatch window). Split the latter into a new /get-started/upgrades page and cross-link the two, updating references elsewhere accordingly. Also links Upgrades from the Releases page's intro paragraph, so readers land on release notes and know where to find the how-to for applying them. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
mfal
changed the title
Jan-Eimertenbrink
left a comment
Jan-Eimertenbrink
left a comment
Member
There was a problem hiding this comment.
Mini: Versionierung sollte im Get Started Menü über Upgrades stehen
Both pages were unlisted in CONTENT_ORDER, so the sidebar sorted them alphabetically by label — Upgrades before Versionierung. Author the full Get Started child order explicitly instead (all-or-nothing per contentOrder.node.test.ts), putting Versionierung ahead of Upgrades per review feedback on #3064. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Member
Author
|
Fixed — Get Started now sorts explicitly (Installation, Stylesheet, Versionierung, Upgrades) via 🤖 Addressed by Claude Code |
1 similar comment
Member
Author
|
Fixed — Get Started now sorts explicitly (Installation, Stylesheet, Versionierung, Upgrades) via 🤖 Addressed by Claude Code |
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
2 participants
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
/get-started/upgradespage: the migration-guide pointer, the codemod CLI section, deprecation-warning guidance, and the post-release npm version-mismatch window.Versionierungkeeps the semver contract itself (what's guaranteed, Node/React support, lifecycle status).installation,align, andsegmented-controlto point at whichever of the two now actually covers that content.Upgradesfrom theReleasespage's intro paragraph (both the rendered page and its shadow MDX used for search/llms.txt), so readers landing on release notes know where to find the upgrade how-to.Test plan
pnpm nx test:links docs— passespnpm nx build docs(full production build) — passes; verified/get-started/upgradesis generated, TypeScript compiles, and the split content lands on the right page in the built HTMLprettier --checkon the touched files — passes