Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion platforms/web/apps/storybook/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@
"@storybook/addon-docs": "10.2.10",
"@storybook/addon-themes": "10.2.10",
"@storybook/addon-vitest": "10.2.10",
"@storybook/react": "10.2.10",
"@storybook/react": "10.3.3",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Upgrade Storybook renderer and framework together

Bumping only @storybook/react to 10.3.3 while leaving @storybook/react-vite at 10.2.10 creates a split Storybook runtime: the lockfile now contains both @storybook/react@10.3.3 and @storybook/react@10.2.10 (pulled in by @storybook/react-vite@10.2.10). In this setup, Storybook’s Vite framework can continue executing against the older renderer path, so the security update is incomplete and version-skew bugs can appear at runtime/tests due to mixed internal APIs.

Useful? React with 👍 / 👎.

"@storybook/react-vite": "10.2.10",
"@storybook/test": "^8.6.15",
"@tailwindcss/vite": "4.1.18",
Expand Down
Loading
Loading