CLI: Fixed broken migration guide link#32148
Merged
Merged
Conversation
Package BenchmarksCommit: No significant changes detected, all good. 👏 |
jonniebigodes
approved these changes
Aug 5, 2025
Contributor
jonniebigodes
left a comment
There was a problem hiding this comment.
@selenehyun, thank you for putting together this pull request and helping us fix this issue with the link in the CLI. Appreciate it 🙏 ! I've checked, and all is good on my end.
More than glad to merge this once the checklist clears.
Hope you have a fantastic day.
Stay safe
|
View your CI Pipeline Execution ↗ for commit 404c4f3
☁️ Nx Cloud last updated this comment at |
8 tasks
8 tasks
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.
Closes #
What I did
Updated the migration guide URL in
cli-storybook’supgrade.ts.The previous link:
has been corrected to:
This ensures users are directed to the correct migration guide after running the upgrade.
Checklist for Contributors
Testing
The changes in this PR are covered in the following automated tests:
Manual testing
No manual testing is required for this change.
Optionally, you may run the
upgradecommand and verify that the log displays the updated URL.Documentation
Checklist for Maintainers
When this PR is ready for testing, make sure to add
ci:normal,ci:mergedorci:dailyGH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found incode/lib/cli-storybook/src/sandbox-templates.tsMake sure this PR contains one of the labels below:
Available labels
bug: Internal changes that fixes incorrect behavior.maintenance: User-facing maintenance tasks.dependencies: Upgrading (sometimes downgrading) dependencies.build: Internal-facing build tooling & test updates. Will not show up in release changelog.cleanup: Minor cleanup style change. Will not show up in release changelog.documentation: Documentation only changes. Will not show up in release changelog.feature request: Introducing a new feature.BREAKING CHANGE: Changes that break compatibility in some way with current major version.other: Changes that don't fit in the above categories.🦋 Canary release
This PR does not require a canary release.
Greptile Summary
This PR fixes a broken documentation link in the Storybook CLI upgrade command. The change updates a single URL reference in the
upgrade.tsfile fromhttps://storybook.js.org/docs/migration-guidetohttps://storybook.js.org/docs/releases/migration-guide. This URL appears in the post-upgrade logging message that directs users to the migration guide for understanding changes after runningstorybook upgrade.The fix addresses a user experience issue where the upgrade command was displaying a broken link (404 error) instead of directing users to the correct migration documentation. This logging occurs in the
logUpgradeResultsfunction, which provides helpful resources to users after they complete a Storybook upgrade. The corrected URL ensures users can access the migration guide documentation to understand the changes and steps needed for their upgrade.Confidence score: 5/5
Context used:
Context - In the documentation, ensure that the links to the builder's documentation and the Next.js framework documentation are correct and not broken. (link)