Docs: Fix broken link in migration guide

[kylegach]

What I did

Corresponds with #32196

Checklist for Contributors

Testing

Manual testing

1. Confirm the updated link is correct

Documentation

• Add or update documentation reflecting your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Checklist for Maintainers

• When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli-storybook/src/sandbox-templates.ts

• Make 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.

Greptile Summary

This PR fixes a broken internal link in the Storybook migration guide documentation. The change updates a relative path from ../configure/upgrading.mdx to ./upgrading.mdx on line 59 of the migration guide file. This addresses a 404 error that was occurring after documentation restructuring where migration guides were moved under the /docs/releases/ path.

The fix is straightforward - it corrects the link reference to point to the upgrading documentation within the same releases directory instead of trying to navigate to a non-existent configure directory. This ensures users can successfully access upgrade instructions when following links from the migration guide. The change aligns with Storybook's documentation structure and maintains the user experience by providing working navigation between related documentation pages.

Confidence score: 5/5

• This PR is extremely safe to merge with no risk of breaking functionality
• Score reflects a simple documentation link fix with clear intent and minimal complexity
• No files require special attention as this is a single-line documentation correction

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)

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 022ad9e

Command	Status	Duration	Result
nx run-many -t build --parallel=3	✅ Succeeded	1m 13s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-08-05 20:17:55 UTC