docs(codemods): add migration entry for Tabs' navigation-usage move to TabNavigation - #3062
Merged
Merged
Conversation
…o TabNavigation Tabs' rendering changed in 0.2.0-alpha.977 (the same release that introduced TabNavigation): full-width equal tabs with a shared sliding indicator replaced the old fit-content, individually-highlighted tabs. Consumers who exploited Tabs' inherited React Aria routing props (href/target/routerOptions on TabTitle) to fake real navigation should move that usage to TabNavigation, which was built for it and deliberately kept the old Tabs look. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Contributor
Coverage Report for ./packages/components/
File CoverageNo changed files found. |
mfal
enabled auto-merge (squash)
September 1, 2026 13:59
Contributor
🚀 Preview DeploymentPreview environments are ready:
Images:
|
…igration entry Tabs collapses all-at-once (the whole tab list turns into a single button opening a context menu with every tab), while TabNavigation collapses incrementally (items hide one by one into a "More" menu as space runs out). The entry previously claimed both collapse the same way. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Jan-Eimertenbrink
approved these changes
Sep 1, 2026
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
Tabs' rendering changed in0.2.0-alpha.977(the same release that introducedTabNavigation): full-width equal tabs with a shared sliding indicator replaced the previous fit-content tabs with per-tab static hover/pressed/selected backgrounds.Tabsused to switch content within a page.Tabs/TabTitle's inherited React Aria routing props (href/target/routerOptions) to fake real navigation should move that usage toTabNavigation, which was built for exactly this and deliberately kept the oldTabslook and feel.Tabsusage was real navigation or a genuine content switcher can't be derived from the source alone, same reasoning as the existingSegmentedControldeprecation entry.Files
packages/codemods/src/migrations/tabs-navigation-usage-to-tab-navigation/entry.md(new catalogue entry)packages/codemods/src/tests/remoteScope.test.ts(registers the entry's remote-package targets)packages/codemods/src/migrations.generated.ts,packages/components/MIGRATION.md(regenerated viapnpm nx build codemods)Test plan
pnpm nx build codemods— regeneratesmigrations.generated.tsandMIGRATION.mdpnpm nx test:unit codemods— 308/308 tests pass, including the catalogue/remote-scope consistency checksprettier --checkon touched files🤖 Generated with Claude Code