Docs: Set init/upgrade snippets to next on next #29696
Merged
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.
Setting the init/upgrade snippets to
nextso that we can have users test prereleases like@storybook/react-native-web-vite. @kylegach / @jonniebigodes we need to add a release checklist item to ensure that these are alwayslatestonmain.🦋 Canary release
This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the
@storybookjs/coreteam here.core team members can create a canary release here or locally with
gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>Greptile Summary
Updates initialization and upgrade command snippets in documentation to use
@nexttag instead of@latest, enabling users to test prerelease versions of Storybook packages.docs/_snippets/init-command.mdto use@nexttag for npx, pnpm, and yarn initialization commandsdocs/_snippets/storybook-upgrade.mdto use@nexttag for upgrade commands across all package managers@lateston main branch