Repository navigation
chore: update to Storybook 11.0.0-beta.2 - #970
Merged
Merged
Conversation
🦋 Changeset detectedLatest commit: 485c834 The changes in this PR will be included in the next version bump. This PR includes changesets to release 9 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
Updates the Storybook packages from 11.0.0-beta.1 to 11.0.0-beta.2. No code changes are needed.
What changed upstream, and why it doesn't affect us
I read the full
v11.0.0-beta.1...v11.0.0-beta.2diff, not just the release notes. The code the device runtime uses (preview-api,channels,csf,csf-tools,core-events) is unchanged. The rest:addonsand types fromstorybook/manager-api, not its store.experimental_manifestswithout presets, so it stays on the react-docgen path and never resolves a docgen TypeScript package.docs-showanddocs-show-storynow add astorybookIdinput only when the request's sources compose several Storybooks. We register the tools for a single Storybook, so the inputs are unchanged.features.experimentalLiveServerSnippetsflag, which is off by default.@joshwooding/vite-plugin-react-docgen-typescript.@storybook/codemod. This is most of the lockfile shrink.['Laptop', 'Book', 'Whiskey']with one space between items, which shows in MCPdocs-showoutput.Changes
storybook,@storybook/react,@storybook/react-native-web-viteand@storybook/mcpmoved to^11.0.0-beta.2in every package and example, viapnpm update-storybook-deps --version '^11.0.0-beta.2'.pnpm dedupe. Without it, ondevice-notes' auto-installed@storybook/reactpeer stayed on beta.1.^11.0.0-beta.1, because nothing in beta.2 needs a higher minimum.@storybook/react-native, since its@storybook/reactand@storybook/mcpdependencies change.Checks
pnpm build,test,check:types,lint,format:checkandrepo:lintall pass.Device testing
examples/expo-example, Expo SDK 58 / React Native 0.88 dev builds, on an iPhone 17e simulator (iOS 27) and a Pixel 9 emulator (Android 15):updateStoryArgsupdates the rendered story and the Controls panel.MCP server
Called
POST /mcpon the running channel server:tools/listreturnsdocs-list,docs-show,docs-show-story,get-storybook-story-instructionsandselect-story.docs-list(withwithStoryIds),docs-showanddocs-show-storyreturn the example's components, props and story code.select-storychanged the story on both devices.Not part of this PR
storybook buildfor the web Storybook inexamples/expo-examplefails, onnextas well. react-native-svg 15.16'sresolveAssetUri.web.jsimports@react-native/assets-registry/registry, which React Native 0.88 no longer installs. That needs a separate fix.