-
Notifications
You must be signed in to change notification settings - Fork 35
chore(deps-dev): bump storybook from 9.1.15 to 10.0.0 #527
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
Conversation
✅ Deploy Preview for fireproof-ai-builder ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "@types/react": "~19.2.2", | ||
| "@types/react-dom": "~19.1.0", | ||
| "@vitest/browser-playwright": "^4.0.2", | ||
| "storybook": "^9.1.6", | ||
| "storybook": "^10.0.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Align Storybook addons with v10 upgrade
The commit bumps storybook to 10.0.0 but leaves the related packages (@storybook/react, @storybook/react-vite, @storybook/addon-*) pinned to 9.1.x. Storybook’s packages are versioned in lockstep and v10 switched the entire suite to ESM-only; running the v10 CLI with v9 framework/addons generally throws module resolution errors or builder mismatches when invoking pnpm storybook. Please bump the @storybook/* devDependencies to v10 as well so the framework and addons match the new major release.
Useful? React with 👍 / 👎.
| "netlify-cli": "^23.9.1", | ||
| "prettier": "^3.6.2", | ||
| "shiki": "^3.2.1", | ||
| "storybook": "^9.1.6", | ||
| "storybook": "^10.0.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update main app Storybook packages to v10
Similar to the base package, the main application now depends on storybook 10.0.0 while @storybook/react, @storybook/react-vite, and the addons remain constrained to the 9.1.x series. Because Storybook 10’s CLI and builder expect matching v10 framework packages, this version skew is likely to break the dev server or build (ERR_REQUIRE_ESM/API mismatch). The @storybook/* devDependencies here should be bumped to ^10.0.0 to keep the toolchain consistent.
Useful? React with 👍 / 👎.
|
Dependabot can't parse your pnpm-lock.yaml. Because of this, Dependabot cannot update this pull request. |
1 similar comment
|
Dependabot can't parse your pnpm-lock.yaml. Because of this, Dependabot cannot update this pull request. |
Bumps [storybook](https://github.com/storybookjs/storybook/tree/HEAD/code/core) from 9.1.15 to 10.0.0. - [Release notes](https://github.com/storybookjs/storybook/releases) - [Changelog](https://github.com/storybookjs/storybook/blob/next/CHANGELOG.md) - [Commits](https://github.com/storybookjs/storybook/commits/v10.0.0/code/core) --- updated-dependencies: - dependency-name: storybook dependency-version: 10.0.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
fbb00cf to
8d02532
Compare
|
@dependabot rebase |
|
Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry! If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request |
|
@dependabot rebase |
|
Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry! If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |

Bumps storybook from 9.1.15 to 10.0.0.
Release notes
Sourced from storybook's releases.
... (truncated)
Changelog
Sourced from storybook's changelog.
... (truncated)
Commits
88a02e6Bump version from "10.0.0-rc.4" to "10.0.0" [skip ci]05d448bBump version from "10.0.0-rc.3" to "10.0.0-rc.4" [skip ci]1c0424fMerge pull request #32793 from ia319/bug/32630-instrumenter-debug-state-reset239794eMerge pull request #32859 from storybookjs/shilman/first-load-new-user0ff3fd8Merge branch 'next' into shilman/first-load-new-userac21b0aTelemetry: Add new user info to preview-first-load1d4ca46Merge branch 'next' into bug/32630-instrumenter-debug-state-reset7a5bb32add experimental_devServer preset1aaa3a3Merge branch 'next' into fix-core-resolve-scoped-frameworkc144ed0chore: fix unit testsDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)