build(deps-dev): bump @storybook/react-vite from 10.4.6 to 10.5.5 - #759
build(deps-dev): bump @storybook/react-vite from 10.4.6 to 10.5.5#759dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@storybook/react-vite](https://github.com/storybookjs/storybook/tree/HEAD/code/frameworks/react-vite) 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/frameworks/react-vite) --- updated-dependencies: - dependency-name: "@storybook/react-vite" dependency-version: 10.5.5 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
|
Warning Review limit reached
Next review available in: 59 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
Comment |
![opencode-agent[bot]](https://avatars.githubusercontent.com/in/1549082?s=60&v=4){kind=small}
There was a problem hiding this comment.
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
successwith required evidence or explicit no-source not-applicable evidence. -
Regression test: Keep the approval branch checking
needs.coverage-evidence.result == successbefore 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 head3dcda62c540a81b0a716122ba7b59b3908420327. -
Head SHA:
3dcda62c540a81b0a716122ba7b59b3908420327 -
Workflow run: 31057082967
-
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"]
OpenCode Review Overview
Pull request overviewOpenCode cannot approve yet because required coverage evidence did not pass. Review outcome1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence
Coverage evidenceCoverage evidence job did not run or did not publish coverage evidence. Changed-File Evidence Mapflowchart 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"]
|
|
@coderabbitai review Review the exact live head only. Verify Storybook React-Vite 10.5.5 and every related lockfile entry remain mutually compatible, the ws security remediation is resolved, stories/docs/a11y interactions and visual-test configuration remain intact, and lint, strict typecheck, complete tests/coverage, Storybook and production builds, audit, and security gates pass. Review only; do not update the branch, merge, release, or alter protections. |
Rate Limit Exceeded
|
|
@opencode-agent address Use this PR as the single aligned Storybook maintenance slice; do not merge current head The current generated diff contains unrelated npm classification churn ( |
1 participant
Bumps @storybook/react-vite from 10.4.6 to 10.5.5.
Release notes
Sourced from @storybook/react-vite's releases.
... (truncated)
Changelog
Sourced from @storybook/react-vite's changelog.
... (truncated)
Commits
05a52b7Bump version from "10.5.4" to "10.5.5" [skip ci]3327dc4Bump version from "10.5.3" to "10.5.4" [skip ci]9ac2739Bump 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]448db85Bump version from "10.5.0-beta.1" to "10.5.0-beta.2" [skip ci]a4ce979Bump version from "10.5.0-beta.0" to "10.5.0-beta.1" [skip ci]f0bf138Bump version from "10.5.0-alpha.11" to "10.5.0-beta.0" [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 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)