Repository navigation
chore(deps-dev): bump storybook from 9.1.20 to 10.5.4 - #414
dependabot[bot] wants to merge 2 commits into
Conversation
Bumps [storybook](https://github.com/storybookjs/storybook/tree/HEAD/code/core) from 9.1.20 to 10.5.4. - [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.5.4/code/core) --- updated-dependencies: - dependency-name: storybook dependency-version: 10.5.4 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Dependabot does not update bun.lock in a Bun workspace (dependabot-core#14223), so `bun install --frozen-lockfile` reds every CI job on its PRs before any real signal is produced. Regenerated from the bumped manifest per the mitigation documented in .github/dependabot.yml.
|
Refreshed The result: this PR cannot pass on its own. It moves |
Storybook only runs when every one of its packages sits on the same major, so a per-package major PR is structurally unmergeable — #413 and #414 each moved half the family and neither could ever go green (see #425). This does not contradict #398's decision to ungroup majors: that rationale was "one migration per PR", and the Storybook family IS one migration whose packages must move in lockstep. Listed first so Dependabot keeps the family together for minor/patch too, which have the same lockstep requirement. Kept as the last commit, touching only this file, so it can be dropped with a single revert without touching the migration.
* chore(web): move the whole Storybook family to 10.5.5 in lockstep Storybook refuses to run unless every one of its packages sits on the same major, so `storybook`, `@storybook/react-vite`, `@storybook/addon-vitest` and `@storybook/addon-a11y` all move together in one change. Splitting them is what made the two Dependabot PRs structurally unmergeable: #413 moved the framework and died on `No matching export ... "Tag"` against core 9, #414 moved core only and made bun resolve a nested storybook@9 under every `@storybook/*` package. `bun pm ls --all` now shows exactly one core (storybook@10.5.5) and no nested copies, and `bun install --frozen-lockfile` is clean. * docs(web): record why setProjectAnnotations stays after the Storybook 10 bump addon-vitest 10.3+ prints an INFO box telling you to delete this call because it now provisions preview annotations itself. That is true only for the `storybook` Vitest project (the one with the plugin). The `unit` project shares this setup file and has no Storybook plugin, so following the nudge would strip the preview decorators from every composed-story unit test. * docs(web): correct the react-dom-shim entry name in the CI-freeze guards @storybook/react-dom-shim ships dist/react-18.js in Storybook 10 (it was dist/react-18.mjs in 9). Both optimizeDeps guard comments named the old file; the guard itself is unchanged (it pre-bundles by package name), only the explanation of WHICH module it covers was stale. * chore(ci): group the Storybook family in Dependabot, majors included Storybook only runs when every one of its packages sits on the same major, so a per-package major PR is structurally unmergeable — #413 and #414 each moved half the family and neither could ever go green (see #425). This does not contradict #398's decision to ungroup majors: that rationale was "one migration per PR", and the Storybook family IS one migration whose packages must move in lockstep. Listed first so Dependabot keeps the family together for minor/patch too, which have the same lockstep requirement. Kept as the last commit, touching only this file, so it can be dropped with a single revert without touching the migration.
|
Superseded by #449, which migrated the whole Storybook family to 10.5.5 in lockstep (merged). This PR could never pass on its own — Storybook requires every package on the same major, and each of #413/#414 moved only half the family. #413 pulled Worth recording: the
|
|
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. |
1 participant
Bumps storybook from 9.1.20 to 10.5.4.
Release notes
Sourced from storybook's releases.
... (truncated)
Changelog
Sourced from storybook's changelog.
... (truncated)
Commits
3327dc4Bump version from "10.5.3" to "10.5.4" [skip ci]3f07eb7Merge pull request #35560 from storybookjs/norbert/fix-rn-telemetry-metadata22e3666Merge pull request #35541 from hxy-asdw/fix/prismjs-dark-mode-contrast-355409ac2739Bump version from "10.5.2" to "10.5.3" [skip ci]b4b00f2Merge pull request #34971 from storybookjs/valentin/upgrade-typescript-6518f711Bump version from "10.5.1" to "10.5.2" [skip ci]c253a06Bump version from "10.5.0" to "10.5.1" [skip ci]9dafcd2Bump version from "10.5.0-beta.2" to "10.5.0" [skip ci]705d4b0Fix windows UTs for 10.512a9299Merge pull request #35398 from storybookjs/sidnioulz/agentic-review-a11yDependabot 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)