-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
CLI: Remove Storybook dependencies before adding re-adding them #30600
CLI: Remove Storybook dependencies before adding re-adding them #30600
Conversation
View your CI Pipeline Execution ↗ for commit 8457f7a.
☁️ Nx Cloud last updated this comment at |
Package BenchmarksCommit: No significant changes detected, all good. 👏 |
4c65bea
to
0b06a97
Compare
0b06a97
to
7672b95
Compare
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.
1 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings | Greptile
Failed to publish canary version of this pull request, triggered by @valentinpalkovic. See the failed workflow run at: https://github.com/storybookjs/storybook/actions/runs/13455898257 |
fd3d3e6
to
8457f7a
Compare
Closes #30306
What I did
Users struggle to upgrade Storybook with npm because of conflicting peer-dependencies. This issue doesn't occur when Storybook is freshly installed. It seems that npm has issues to upgrade all dependencies at once.
Solution:
storybook
package, because other third-party Storybook integrations may depend on thestorybook
package.Context:
npx storybook@latest upgrade
#30306Checklist for Contributors
Testing
The changes in this PR are covered in the following automated tests:
Manual testing
This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!
Documentation
MIGRATION.MD
Checklist for Maintainers
When this PR is ready for testing, make sure to add
ci:normal
,ci:merged
orci:daily
GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found incode/lib/cli-storybook/src/sandbox-templates.ts
Make sure this PR contains one of the labels below:
Available labels
bug
: Internal changes that fixes incorrect behavior.maintenance
: User-facing maintenance tasks.dependencies
: Upgrading (sometimes downgrading) dependencies.build
: Internal-facing build tooling & test updates. Will not show up in release changelog.cleanup
: Minor cleanup style change. Will not show up in release changelog.documentation
: Documentation only changes. Will not show up in release changelog.feature request
: Introducing a new feature.BREAKING CHANGE
: Changes that break compatibility in some way with current major version.other
: Changes that don't fit in the above categories.🦋 Canary release
This pull request has been released as version
0.0.0-pr-30600-sha-4c65bea0
. Try it out in a new sandbox by runningnpx [email protected] sandbox
or in an existing project withnpx [email protected] upgrade
.More information
0.0.0-pr-30600-sha-4c65bea0
valentin/uninstall-dependencies-during-upgrade-for-npm-users
4c65bea0
1740059726
)To request a new release of this pull request, mention the
@storybookjs/core
team.core team members can create a new canary release here or locally with
gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=30600
Greptile Summary
This PR modifies the Storybook upgrade process to handle npm-specific dependency conflicts by removing and reinstalling Storybook packages during upgrades.
code/lib/cli-storybook/src/upgrade.ts
to remove all Storybook dependencies except the core 'storybook' package before reinstallationnpx storybook@latest upgrade
#30306 for npm users