Incrementally upgrade React Native Storybook across the supported migration paths. Use when upgrading `@storybook/react-native` projects from 5.3.x to 6.5.x, 6.5.x to 7.6.x, 7.6.x to 8.3.x, 8.x to 9.x, or 9.x to 10.x. Detect the currently installed Storybook version, choose only the next migration step, update dependencies and config, regenerate `storybook.requires`, convert remaining `storiesOf` stories to CSF during the `6.5.x -> 7.6.x` upgrade, and stop after a single version hop instead of jumping multiple major versions at once.
Upgrade one supported version step at a time. Do not jump from an older major directly to the latest release in a single pass.
package.json, lockfiles, and config files before editing anything.6.5.x -> 7.6.x step, convert any remaining storiesOf stories to CSF instead of preserving compatibility mode.Look at these signals together:
package.json versions for @storybook/react-native, storybook, @storybook/react, and @storybook/addon-ondevice-*.storybook/.rnstorybook/metro/withStorybook, metro/withStorybookConfig, or default-vs-named withStorybookstoriesOfstorybook.requires.js vs storybook.requires.tsIf the version is ambiguous, stop and clarify the current installed version instead of guessing.
Use exactly one reference file:
9.x -> 10.x: references/from-9-to-10.md8.x -> 9.x: references/from-8-to-9.md7.6.x -> 8.3.x: references/from-7-6-to-8-3.md6.5.x -> 7.6.x: references/from-6-5-to-7-6.md5.3.x -> 6.5.x: references/from-5-3-to-6-5.mdstorybook.requires or restart Metro when that step requires it.When you finish a migration step, report: