Bump storybook from 10.1.11 to 10.2.13 in the npm_and_yarn group across 1 directory - #14
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps the npm_and_yarn group with 1 update in the / directory: [storybook](https://github.com/storybookjs/storybook/tree/HEAD/code/core). Updates `storybook` from 10.1.11 to 10.2.13 - [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.2.13/code/core) --- updated-dependencies: - dependency-name: storybook dependency-version: 10.2.13 dependency-type: direct:development dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
galangel
added a commit
that referenced
this pull request
Aug 18, 2026
Supersedes #14, which had been open since February with a conflicting lockfile and could not be merged as-is. Addresses the high-severity advisory "Storybook Dev Server is Vulnerable to WebSocket Hijacking" (vulnerable >= 10.0.0-beta.0 < 10.2.10, patched in 10.2.10). npm audit now reports no storybook advisories. Why 10.4.6 rather than latest (10.5.9): storybook 10.5.x declares `peerOptional vite-plus@^0.1.15 || ^0.2.0`, and npm resolves that to vite-plus 0.2.9, which peer-requires @vitest/browser-playwright@4.1.10 exactly. This project pins vitest 4.0.16, whose own browser-playwright peer is 4.0.16, so 10.5.x cannot resolve without also bumping vitest. 10.4.6 declares vite-plus ^0.1.15, which resolves cleanly against the current vitest. Bumping vitest is a larger change and does not belong in a security patch. Why all four packages move together, unlike #14: #14 bumped only storybook core to 10.2.13 and left @storybook/addon-docs, @storybook/react-vite and eslint-plugin-storybook at 10.1.11. Their peer ranges (^10.1.11) do permit that, so it was not broken, but keeping the family on one version avoids mixed-version surprises. Ranges use ~10.4.6 rather than ^10.4.6 deliberately: a caret would let npm resolve to 10.5.x and reintroduce the vite-plus conflict on the next lockfile regeneration. The tilde also raises the declared floor above the vulnerable range, which ^10.1.11 did not do. The lockfile is regenerated by npm from main's lockfile plus the new package.json ranges, and `npm ci` is verified to succeed against it. Verified locally against the CI steps: npm ci, typecheck, lint (0 errors, 2 pre-existing warnings), format:check, test:coverage (354 tests, 19 files passing), build, and build:storybook all pass. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
galangel
added a commit
that referenced
this pull request
Aug 18, 2026
…ry (#20) Supersedes #14, which had been open since February with a conflicting lockfile and could not be merged as-is. Addresses the high-severity advisory "Storybook Dev Server is Vulnerable to WebSocket Hijacking" (vulnerable >= 10.0.0-beta.0 < 10.2.10, patched in 10.2.10). npm audit now reports no storybook advisories. Why 10.4.6 rather than latest (10.5.9): storybook 10.5.x declares `peerOptional vite-plus@^0.1.15 || ^0.2.0`, and npm resolves that to vite-plus 0.2.9, which peer-requires @vitest/browser-playwright@4.1.10 exactly. This project pins vitest 4.0.16, whose own browser-playwright peer is 4.0.16, so 10.5.x cannot resolve without also bumping vitest. 10.4.6 declares vite-plus ^0.1.15, which resolves cleanly against the current vitest. Bumping vitest is a larger change and does not belong in a security patch. Why all four packages move together, unlike #14: #14 bumped only storybook core to 10.2.13 and left @storybook/addon-docs, @storybook/react-vite and eslint-plugin-storybook at 10.1.11. Their peer ranges (^10.1.11) do permit that, so it was not broken, but keeping the family on one version avoids mixed-version surprises. Ranges use ~10.4.6 rather than ^10.4.6 deliberately: a caret would let npm resolve to 10.5.x and reintroduce the vite-plus conflict on the next lockfile regeneration. The tilde also raises the declared floor above the vulnerable range, which ^10.1.11 did not do. The lockfile is regenerated by npm from main's lockfile plus the new package.json ranges, and `npm ci` is verified to succeed against it. Verified locally against the CI steps: npm ci, typecheck, lint (0 errors, 2 pre-existing warnings), format:check, test:coverage (354 tests, 19 files passing), build, and build:storybook all pass. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
Author
|
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests. To ignore these dependencies, configure ignore rules in dependabot.yml |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/npm_and_yarn-ae085b4777
branch
August 18, 2026 11:30
galangel
added a commit
that referenced
this pull request
Aug 18, 2026
…ry (#20) Supersedes #14, which had been open since February with a conflicting lockfile and could not be merged as-is. Addresses the high-severity advisory "Storybook Dev Server is Vulnerable to WebSocket Hijacking" (vulnerable >= 10.0.0-beta.0 < 10.2.10, patched in 10.2.10). npm audit now reports no storybook advisories. Why 10.4.6 rather than latest (10.5.9): storybook 10.5.x declares `peerOptional vite-plus@^0.1.15 || ^0.2.0`, and npm resolves that to vite-plus 0.2.9, which peer-requires @vitest/browser-playwright@4.1.10 exactly. This project pins vitest 4.0.16, whose own browser-playwright peer is 4.0.16, so 10.5.x cannot resolve without also bumping vitest. 10.4.6 declares vite-plus ^0.1.15, which resolves cleanly against the current vitest. Bumping vitest is a larger change and does not belong in a security patch. Why all four packages move together, unlike #14: #14 bumped only storybook core to 10.2.13 and left @storybook/addon-docs, @storybook/react-vite and eslint-plugin-storybook at 10.1.11. Their peer ranges (^10.1.11) do permit that, so it was not broken, but keeping the family on one version avoids mixed-version surprises. Ranges use ~10.4.6 rather than ^10.4.6 deliberately: a caret would let npm resolve to 10.5.x and reintroduce the vite-plus conflict on the next lockfile regeneration. The tilde also raises the declared floor above the vulnerable range, which ^10.1.11 did not do. The lockfile is regenerated by npm from main's lockfile plus the new package.json ranges, and `npm ci` is verified to succeed against it. Verified locally against the CI steps: npm ci, typecheck, lint (0 errors, 2 pre-existing warnings), format:check, test:coverage (354 tests, 19 files passing), build, and build:storybook all pass.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the npm_and_yarn group with 1 update in the / directory: storybook.
Updates
storybookfrom 10.1.11 to 10.2.13Release notes
Sourced from storybook's releases.
... (truncated)
Changelog
Sourced from storybook's changelog.
... (truncated)
Commits
305b534Bump version from "10.2.12" to "10.2.13" [skip ci]91e7401Merge pull request #33922 from storybookjs/valentin/fix-performance-in-infer-...68f811fBump version from "10.2.11" to "10.2.12" [skip ci]9d6cde2Merge pull request #33868 from storybookjs/valentin/sanitize-save-from-contro...b13d696Merge pull request #33910 from storybookjs/shilman/add-project-sincebe01dcaBump version from "10.2.10" to "10.2.11" [skip ci]c527821Merge pull request #33888 from storybookjs/valentin/fix-addon-vitest-a11y-set...c812573Bump version from "10.2.9" to "10.2.10" [skip ci]fd275fbMerge pull request #33820 from storybookjs/harden-websocket-security4cdde82Bump version from "10.2.8" to "10.2.9" [skip ci]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 <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.