chore(deps): update dependency storybook to v8.6.15 [security] #3946
Conversation
|
renovate
bot
force-pushed
the
chore/renovate/npm-storybook-vulnerability
branch
16 times, most recently
from
f4b3fd3 to
5c49b91
Compare
renovate
bot
force-pushed
the
chore/renovate/npm-storybook-vulnerability
branch
4 times, most recently
from
9a869ec to
371394e
Compare
renovate
bot
force-pushed
the
chore/renovate/npm-storybook-vulnerability
branch
7 times, most recently
from
bd5d02d to
8af5ade
Compare
renovate
bot
force-pushed
the
chore/renovate/npm-storybook-vulnerability
branch
14 times, most recently
from
3480939 to
2ae8b11
Compare
renovate
bot
force-pushed
the
chore/renovate/npm-storybook-vulnerability
branch
from
2ae8b11 to
035633b
Compare
…orybook-vulnerability * origin/main: chore(deps): update dependency @langchain/core to v1.1.8 [security] (#3958)
renovate
bot
force-pushed
the
chore/renovate/npm-storybook-vulnerability
branch
from
035633b to
f256cc9
Compare
… type 'ReactElement<any, string | JSXElementConstructor<any>>', but multiple children were provided.
…nerability' into chore/renovate/npm-storybook-vulnerability * origin/chore/renovate/npm-storybook-vulnerability: chore(deps): update dependency storybook to v8.6.15 [security]
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
|
SAP employees are expected to use their SAP-email address for commits related to their work. Our compliance check has detected usage of an email other than a SAP one by a SAP employee. Please update your pull request accordingly. If you think this is wrong or need any assistance, please contact [email protected]. |
815are
left a comment
815are
left a comment
There was a problem hiding this comment.
checked:
- code changes straightforward - I do not see issue;
- tested storybooks for three packages and works ok for me
|
2 participants
This PR contains the following updates:
8.4.2→8.6.15Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
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
.envfile, which could, in specific circumstances, lead to those variables being unexpectedly bundled into the artifacts created by thestorybook buildcommand. 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:
storybook builddirectly or indirectly) in a directory that contains a.envfile (including variants like.env.local).envfile contains sensitive secrets7.0.0or aboveStorybooks built without a
.envfile at build time are not affected, including common CI-based builds where secrets are provided via platform environment variables rather than.envfiles.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
.envfiles 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 theenvproperty 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.15Compare Source
v8.6.14Compare Source
v8.6.13Compare Source
react-native-web- #31324, thanks @ndelangen!v8.6.12Compare Source
ember-template-compilerimport for ember 6+ - #30682, thanks @leoeuclids!node_modulesfrom docgen - #30981, thanks @JReinhold!v8.6.11Compare Source
v8.6.10Compare Source
v8.6.9Compare Source
v8.6.8Compare Source
v8.6.7Compare Source
v8.6.6Compare Source
v8.6.5Compare Source
@angular-devkit/build-angularto installed packages - #30790, thanks @kasperpeulen![email protected]- #30784, thanks @JReinhold!crypto.randomUUID- #30781, thanks @JReinhold!v8.6.4Compare Source
node_modulesin stats file - #30711, thanks @JReinhold!v8.6.3Compare Source
v8.6.2Compare Source
v8.6.1Compare Source
v8.6.0Compare 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:
List of all updates
--yesand fix--features- #30534, thanks @ghengeveld!UniversalStoreAPI to sync state/events between multiple environments - #30445, thanks @JReinhold!node_modules- #30643, thanks @ndelangen!addon-essentialsnot working when used withgetAbsolutePath- #30557, thanks @JReinhold!+page.sveltefiles - #30369, thanks @xeho91!vitest.config.tswith workspaces, otherwise createvitest.workspace.ts- #30583, thanks @ghengeveld!v8.5.8Compare Source
esbuild@^0.25- #30574, thanks @JReinhold!v8.5.7Compare Source
v8.5.6Compare Source
v8.5.5Compare Source
v8.5.4Compare Source
v8.5.3Compare Source
globalstoextract()- #30415, thanks @ndelangen!v8.5.2Compare Source
v8.5.1Compare Source
interaction test->component test- #30333, thanks @kylegach!v8.5.0Compare 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:
List of all updates
@vitest/coverage-v8during postinstall if no coverage reporter is installed - #29993, thanks @ghengeveld!vitestdetects missing deps - #29763, thanks @ndelangen!test.includepatterns - #30029, thanks @JReinhold!vitestcrashes - #29751, thanks @ndelangen!vitest.setup.js- #30233, thanks @JReinhold!experimental-nextjs-vite- #29814, thanks @ndelangen!globwithtinyglobby- #29817, thanks @ghengeveld!staticDirswith Vitest - #29811, thanks @ghengeveld!require.resolve- #30026, thanks @ndelangen!storybookcommand - #29480, thanks @toothlessdev!TESTING_MODULE_RUN_ALL_REQUESTfor backward compatibility - #29711, thanks @ghengeveld!ERR_PACKAGE_PATH_NOT_EXPORTEDin@storybook/node-logger- #30093, thanks @JReinhold!scrollIntoViewbehavior and reimplement testing module time rendering - #30044, thanks @ghengeveld!@types/nodetodevDepsconsistently - #30163, thanks @ndelangen!useSharedState- #30259, thanks @JReinhold!react-confettiwith@neoconfetti/react- #30098, thanks @ndelangen!@storybook/testas optional peer dependency - #29754, thanks @yannbf!TooltipLinkListand use it in main menu - #29507, thanks @ghengeveld!optimizeDeps- #30117, thanks @ndelangen!@fs- #28941, thanks @tobiasdiez!Configuration
📅 Schedule: Branch creation - "" in timezone America/Los_Angeles, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.