-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tags: Fix composition with older storybooks #27358
Conversation
☁️ Nx Cloud ReportCI is running/has finished running commands for commit a6bdab7. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 1 targetSent with 💌 from NxCloud. |
I think you would like to bump the index here as well: https://github.com/storybookjs/storybook/blob/next/code/lib/preview-api/src/modules/store/StoryIndexStore.ts#L27. Potentially, all places can refer to the same variable, so that this will not been overseen again |
…position Tags: Fix composition with older storybooks (cherry picked from commit fc915d6)
…position Tags: Fix composition with older storybooks (cherry picked from commit fc915d6)
…position Tags: Fix composition with older storybooks (cherry picked from commit fc915d6)
…position Tags: Fix composition with older storybooks (cherry picked from commit fc915d6)
…position Tags: Fix composition with older storybooks (cherry picked from commit fc915d6)
Closes #27352
What I did
Starting in 8.1, all stories get the
dev
tag by default and users have to opt-out if they want to hide them from the sidebar. Unfortunately, previous versions of Storybook did not add thedev
tag by default, so those stories would be filtered from the sidebar when composed.We don't know the version of the Storybook we're composing, so instead I bumped the index version. When we compose a Storybook with a lower index version, we automatically add the
dev
tag to all stories.react-vite/devault-ts
)Checklist for Contributors
Testing
The changes in this PR are covered in the following automated tests:
Manual testing
To test this fix by hand, fire up the
react-vite/default-ts
(or navigate to it from the CI results) and verify by hand that:🦋 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/core
team 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>