Skip to content
Open
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 packages/allcll-ui/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@
"@vitest/coverage-v8": "^4.0.5",
"eslint-plugin-storybook": "10.0.1",
"playwright": "^1.56.1",
"storybook": "10.1.10",
"storybook": "10.2.10",
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 Update lockfile when bumping Storybook version

This commit changes storybook to 10.2.10 in packages/allcll-ui/package.json but does not update pnpm-lock.yaml (which still resolves storybook@10.1.10 for this importer), so the repository is left with manifest/lockfile drift. Our CI workflows run pnpm i --frozen-lockfile (see .github/workflows/build-deploy.yml and .github/workflows/dev-build-deploy.yml), and with this mismatch that install step will fail before build/deploy.

Useful? React with 👍 / 👎.

"vite": "^7.1.11",
"vite-plugin-svgr": "^4.3.0",
"vite-tsconfig-paths": "5.1.4",
Expand Down