Skip to content

Conversation

@openverse-bot
Copy link
Collaborator

@openverse-bot openverse-bot commented Dec 18, 2025

This PR contains the following updates:

Package Type Update Change
storybook (source) devDependencies minor 8.4.7 -> 8.6.15

GitHub Vulnerability Alerts

CVE-2025-68429

On December 11th, the Storybook team received a responsible disclosure alerting them to a potential vulnerability in certain built and published Storybooks.

The vulnerability is a bug in how Storybook handles environment variables defined in a .env file, which could, in specific circumstances, lead to those variables being unexpectedly bundled into the artifacts created by the storybook build command. When a built Storybook is published to the web, the bundle’s source is viewable, thus potentially exposing those variables to anyone with access. If those variables contained secrets, they should be considered compromised.

Who is impacted?

For a project to be vulnerable to this issue, it must:

  • Build the Storybook (i.e. run storybook build directly or indirectly) in a directory that contains a .env file (including variants like .env.local)
  • The .env file contains sensitive secrets
  • Use Storybook version 7.0.0 or above
  • Publish the built Storybook to the web

Storybooks built without a .env file at build time are not affected, including common CI-based builds where secrets are provided via platform environment variables rather than .env files.

Users' Storybook runtime environments (i.e. storybook dev) are not affected. Deployed applications that share a repo with a project's Storybook are not affected.

Storybook 6 and below are not affected.

Recommended actions

First, Storybook recommends that everyone audit for any sensitive secrets provided via .env files and rotate those keys.

Second, Storybook has released patched versions of all affected major Storybook versions that no longer have this vulnerability. Projects should upgrade their Storybook—on both local machines and CI environments—to one of these versions before publishing again.

  • 10.1.10+
  • 9.1.17+
  • 8.6.15+
  • 7.6.21+

Finally, some projects may have been relying on the undocumented behavior at the heart of this issue and will need to change how they reference environment variables after this update. If a project can no longer read necessary environmental variable values, it can either prefix the variables with STORYBOOK_ or use the env property in Storybook’s configuration to manually specify values. In either case, do not include sensitive secrets as they will be included in the built bundle.

Further information

Details of the vulnerability can be found on the Storybook announcement.


Release Notes

storybookjs/storybook (storybook)

v8.6.15

Compare Source

8.6.15

v8.6.14

Compare Source

v8.6.13

Compare Source

v8.6.12

Compare Source

v8.6.11

Compare Source

v8.6.10

Compare Source

v8.6.9

Compare Source

v8.6.8

Compare Source

v8.6.7

Compare Source

v8.6.6

Compare Source

v8.6.5

Compare Source

v8.6.4

Compare Source

v8.6.3

Compare Source

v8.6.2

Compare Source

v8.6.1

Compare Source

v8.6.0

Compare Source

The 8.6 release focuses on Storybook Test, which brings realtime component, accessibility, and visual UI tests to your favorite component workshop.

Here’s what’s new:

  • 🎁 Storybook Test installer for out-of-the-box tests in new projects
  • 🦾 Accessibility “todo” workflow to systematically fix a11y violations
  • 🗜️ 80% smaller create-storybook package for much faster installs
  • 🧪 Dozens of Test fixes based on user feedback
  • 📕 Docs fixes for table of contents, code snippets, and more
  • 🚨 Key security fixes for Vite and ESbuild
  • 💯 Hundreds more improvements
List of all updates

v8.5.8

Compare Source

v8.5.7

Compare Source

v8.5.6

Compare Source

v8.5.5

Compare Source

v8.5.4

Compare Source

v8.5.3

Compare Source

v8.5.2

Compare Source

v8.5.1

Compare Source

v8.5.0

Compare Source

Storybook 8.5 is packed with powerful features to enhance your development workflow. This release makes it easier than ever to build accessible, well-tested UIs. Here’s what’s new:

  • 🦾 Realtime accessibility tests to help build UIs for everybody
  • 🛡️ Project code coverage to measure the completeness of your tests
  • 🎯 Focused tests for faster test feedback
  • ⚛️ React Native Web Vite framework (experimental) for testing mobile UI⚛️
  • 🎁 Storybook test early access program to level up your testing game
  • 💯 Hundreds more improvements
List of all updates

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@openverse-bot openverse-bot requested a review from a team as a code owner December 18, 2025 19:10
@openverse-bot openverse-bot added dependencies Pull requests that update a dependency file 💻 aspect: code Concerns the software code in the repository 🟨 tech: javascript Involves JavaScript 🟩 priority: low Low priority and doesn't need to be rushed 🧰 goal: internal improvement Improvement that benefits maintainers, not users 🧱 stack: frontend Related to the Nuxt frontend labels Dec 18, 2025
@openverse-bot openverse-bot moved this to 👀 Needs Review in Openverse PRs Dec 18, 2025
@github-actions
Copy link

Playwright failure test results: https://github.com/WordPress/openverse/actions/runs/20348278655

It looks like some of the Playwright tests failed. If you made changes to the frontend UI without updating snapshots, this might be the cause. You can download zipped patches containing the updated snapshots alongside a general trace of the tests under the "Artifacts" section in the above page. They're named in the form *_snapshot_diff and *_test_results respectively.

You can read more on how to use these artifacts in the docs.

If the test is flaky, follow the flaky test triage procedure.

@github-actions
Copy link

Latest k6 run output1

     ✓ status was 200

     checks.........................: 100.00% ✓ 404      ✗ 0   
     data_received..................: 94 MB   389 kB/s
     data_sent......................: 53 kB   218 B/s
     http_req_blocked...............: avg=65.57µs  min=2.29µs   med=5.05µs   max=1.75ms   p(90)=155.58µs p(95)=261.94µs
     http_req_connecting............: avg=47.63µs  min=0s       med=0s       max=1.64ms   p(90)=102.34µs p(95)=165.75µs
     http_req_duration..............: avg=151.23ms min=15.59ms  med=102.55ms max=978.93ms p(90)=336.86ms p(95)=408.8ms 
       { expected_response:true }...: avg=151.23ms min=15.59ms  med=102.55ms max=978.93ms p(90)=336.86ms p(95)=408.8ms 
   ✓ http_req_failed................: 0.00%   ✓ 0        ✗ 404 
     http_req_receiving.............: avg=171.23µs min=50.75µs  med=137.91µs max=3.31ms   p(90)=229.18µs p(95)=306.49µs
     http_req_sending...............: avg=28.6µs   min=8.25µs   med=22.71µs  max=734.09µs p(90)=40.45µs  p(95)=62µs    
     http_req_tls_handshaking.......: avg=0s       min=0s       med=0s       max=0s       p(90)=0s       p(95)=0s      
     http_req_waiting...............: avg=151.03ms min=15.45ms  med=102.36ms max=978.45ms p(90)=336.67ms p(95)=408.5ms 
     http_reqs......................: 404     1.679062/s
     iteration_duration.............: avg=810.66ms min=324.29ms med=878.21ms max=1.68s    p(90)=1.11s    p(95)=1.15s   
     iterations.....................: 76      0.315863/s
     vus............................: 1       min=0      max=6 
     vus_max........................: 60      min=60     max=60

Footnotes

  1. This comment will automatically update with new output each time k6 runs for this PR

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

Labels

💻 aspect: code Concerns the software code in the repository dependencies Pull requests that update a dependency file 🧰 goal: internal improvement Improvement that benefits maintainers, not users 🟩 priority: low Low priority and doesn't need to be rushed 🧱 stack: frontend Related to the Nuxt frontend 🟨 tech: javascript Involves JavaScript

Projects

Status: 👀 Needs Review

Development

Successfully merging this pull request may close these issues.

2 participants