chore(deps-dev): bump @storybook/addon-designs from 10.0.2 to 11.1.4#211
chore(deps-dev): bump @storybook/addon-designs from 10.0.2 to 11.1.4#211dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@storybook/addon-designs](https://github.com/storybookjs/addon-designs) from 10.0.2 to 11.1.4. - [Release notes](https://github.com/storybookjs/addon-designs/releases) - [Changelog](https://github.com/storybookjs/addon-designs/blob/master/CHANGELOG.v1-6.md) - [Commits](https://github.com/storybookjs/addon-designs/compare/v10.0.2...@storybook/addon-designs@11.1.4) --- updated-dependencies: - dependency-name: "@storybook/addon-designs" dependency-version: 11.1.4 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| "@storybook/addon-a11y": "^9.0.18", | ||
| "@storybook/addon-coverage": "^2.0.0", | ||
| "@storybook/addon-designs": "^10.0.2", | ||
| "@storybook/addon-designs": "^11.1.4", |
There was a problem hiding this comment.
🔴 Design-viewer add-on upgraded to a version that only works with a newer Storybook than the project uses
The design-viewer add-on is upgraded to a version (@storybook/addon-designs ^11.1.4 at package.json:48) that only supports the next major Storybook release, while every other Storybook package in the project stays on the previous major, so installing and building the component gallery breaks.
Impact: Developers can no longer reliably install dependencies or start/build the Storybook component gallery, since the tool demands a Storybook version the project does not have.
Peer dependency mismatch between addon-designs 11 and Storybook 9
package-lock.json:2956-2960 shows @storybook/addon-designs@11.1.4 declares peer dependencies of storybook: ^10.0.0 (and @storybook/addon-docs: ^10.0.0). However the project pins the whole Storybook toolchain to 9.x: storybook resolves to 9.0.18 (package-lock.json:15531-15533) and package.json:49-88 keeps @storybook/addon-docs, @storybook/react-vite, storybook, etc. at ^9.0.18. The add-on is actively loaded via .storybook/main.ts:7, so this is not an unused dependency. With npm 7+ (repo requires npm >=10, package.json:102) this produces an ERESOLVE install failure, and even when force-installed the add-on built for Storybook 10 can misbehave at runtime in a Storybook 9 host. The bump should be held until the rest of the Storybook packages are upgraded to v10.
Prompt for agents
The bump of @storybook/addon-designs to ^11.1.4 introduces a peer dependency conflict: addon-designs@11 requires storybook and @storybook/addon-docs at ^10.0.0, but this project is entirely on the Storybook 9 toolchain (storybook, @storybook/react-vite, @storybook/addon-docs, etc. all pinned to ^9.0.18 in package.json, and storybook resolves to 9.0.18 in package-lock.json). The addon is registered in .storybook/main.ts, so it is loaded at build/dev time. Either revert this bump to the 10.x line that supports Storybook 9, or upgrade the entire Storybook toolchain to v10 in the same change so the peer ranges are satisfied.
Was this helpful? React with 👍 or 👎 to provide feedback.
Bumps @storybook/addon-designs from 10.0.2 to 11.1.4.
Release notes
Sourced from @storybook/addon-designs's releases.
Commits
29be6a9Merge pull request #300 from storybookjs/changeset-release/master655e47eVersion Packagese98bfa4Merge pull request #299 from storybookjs/fix/release-script13bb222Realign package version with npm after auto->changesets migratione68cc7bFix release script so changeset publish actually runsca26ecdMerge pull request #298 from storybookjs/fix/ghpages-deprecated-actions7eb986dFix GitHub Pages deploy using deprecated artifact actions96a80c3Merge pull request #297 from storybookjs/changeset-release/masterc9493efVersion Packagesdafa82fMerge pull request #296 from storybookjs/changeset/fix-repository-metadata-urlMaintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for
@storybook/addon-designssince your current version.Dependabot 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 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)