Skip to content

build(deps-dev): bump storybook from 10.4.6 to 10.5.5 - #763

Open
dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/npm_and_yarn/develop/storybook-10.5.5
Open

build(deps-dev): bump storybook from 10.4.6 to 10.5.5#763
dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/npm_and_yarn/develop/storybook-10.5.5

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 4, 2026

Copy link
Copy Markdown
Contributor

Bumps storybook from 10.4.6 to 10.5.5.

Release notes

Sourced from storybook's releases.

v10.5.5

10.5.5

v10.5.4

10.5.4

v10.5.3

10.5.3

v10.5.2

10.5.2

v10.5.1

10.5.1

v10.5.0

10.5.0

Foundational changes for new AI workflows

Storybook 10.5 contains hundreds of fixes and improvements:

  • ⚡️ Angular-vite framework: Modern, fast dev, docs, and test (preview)
  • 🌈 Vitest initialGlobals: Test across themes, viewports, locales

... (truncated)

Changelog

Sourced from storybook's changelog.

10.5.5

10.5.4

10.5.3

10.5.2

  • TanStack: Fix createServerFn validator mock - #35185, thanks @​sjh9714!
  • TanStack: Support pathless layout routes (id-only) in story routing - #35465, thanks @​unpunnyfuns!
  • Tanstack-react: Add missing Hydrate export - #35111, thanks @​arun-357!
  • Tanstack-react: Keep JSX-only component references during dead-code elimination - #35206, thanks @​yatishgoel!
  • Vitest: Fix coverage toggle crash on Vite 6 by clearing closed Vitest instance on restart - #35461, thanks @​yannbf!

10.5.1

10.5.0

Foundational changes for new AI workflows

Storybook 10.5 contains hundreds of fixes and improvements:

  • ⚡️ Angular-vite framework: Modern, fast dev, docs, and test (preview)
  • 🌈 Vitest initialGlobals: Test across themes, viewports, locales
  • 🤖 Agentic review: AI-curated visual changesets and search results (experimental)
  • ⚛️ React docgen service: Unified metadata across MCP, Docs, and Controls (experimental)
  • 🧑‍💻 Claude / Codex plugins: One-click ADE integration (experimental)

... (truncated)

Commits
  • 05a52b7 Bump version from "10.5.4" to "10.5.5" [skip ci]
  • 201e77a Merge pull request #35512 from storybookjs/yann/ai-setup-msw-v3
  • cac1e6d Merge pull request #35584 from storybookjs/norbert/upgrade-ws-8.21
  • 9166a91 Merge pull request #35567 from ia319/bug/35566-npm-12-registry-flags
  • 3327dc4 Bump version from "10.5.3" to "10.5.4" [skip ci]
  • 3f07eb7 Merge pull request #35560 from storybookjs/norbert/fix-rn-telemetry-metadata
  • 22e3666 Merge pull request #35541 from hxy-asdw/fix/prismjs-dark-mode-contrast-35540
  • 9ac2739 Bump version from "10.5.2" to "10.5.3" [skip ci]
  • b4b00f2 Merge pull request #34971 from storybookjs/valentin/upgrade-typescript-6
  • 518f711 Bump version from "10.5.1" to "10.5.2" [skip ci]
  • Additional commits viewable in compare view

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [storybook](https://github.com/storybookjs/storybook/tree/HEAD/code/core) from 10.4.6 to 10.5.5.
- [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.5/code/core)

---
updated-dependencies:
- dependency-name: storybook
  dependency-version: 10.5.5
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 4, 2026
@dependabot
dependabot Bot requested a review from seonghobae as a code owner August 4, 2026 17:25
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 4, 2026
@coderabbitai

coderabbitai Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@dependabot[bot], you've reached your PR review limit, so we couldn't start this review.

Next review available in: 58 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: bca8ca9c-375f-4ffe-bb6f-cd228146234a

📥 Commits

Reviewing files that changed from the base of the PR and between acdbea6 and 0c22ed3.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • apps/desktop/package.json

Comment @coderabbitai help to get the list of available commands.

@opencode-agent opencode-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

  • Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

  • Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

  • Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

  • Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

  • Result: REQUEST_CHANGES

  • Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 0c22ed3468aac314e1cb57150b4d2bdbe927da5f.

  • Head SHA: 0c22ed3468aac314e1cb57150b4d2bdbe927da5f

  • Workflow run: 31091674303

  • Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (2 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (2 files)"]
  R1 --> V1["required checks"]
Loading

@opencode-agent

opencode-agent Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

OpenCode Review Overview

  • Head SHA: 0c22ed3468aac314e1cb57150b4d2bdbe927da5f
  • Workflow run: 31091674303
  • Workflow attempt: 1
  • Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

  • Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

  • Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

  • Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

  • Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

  • Result: REQUEST_CHANGES

  • Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 0c22ed3468aac314e1cb57150b4d2bdbe927da5f.

  • Head SHA: 0c22ed3468aac314e1cb57150b4d2bdbe927da5f

  • Workflow run: 31091674303

  • Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (2 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (2 files)"]
  R1 --> V1["required checks"]
Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants