chore(deps): update dependency storybook to v7.6.21 [security]#313
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
chore(deps): update dependency storybook to v7.6.21 [security]#313renovate[bot] wants to merge 1 commit intomainfrom
renovate[bot] wants to merge 1 commit intomainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
renovate
bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
from
d620e12 to
9f444b9
Compare
renovate
bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
from
9f444b9 to
14483a1
Compare
renovate
bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
from
14483a1 to
d3dd922
Compare
renovate
bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
from
d3dd922 to
0699797
Compare
renovate
bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
from
0699797 to
95d5cf2
Compare
renovate
bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
from
95d5cf2 to
51805d0
Compare
renovate
bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
from
51805d0 to
77bd8cd
Compare
renovate
bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
from
77bd8cd to
6e94429
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
2 times, most recently
from
6e94429 to
7b6caa4
Compare
renovate
bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
from
7b6caa4 to
ed17813
Compare
|
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.
This PR contains the following updates:
7.5.3→7.6.21GitHub 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)
v7.6.21Compare Source
v7.6.20Compare Source
v7.6.19Compare Source
7.6.19
7.6.18containing wrong dependency identifiers, thanks @jreinhold!v7.6.18Compare Source
7.6.18
v7.6.17Compare Source
v7.6.16Compare Source
v7.6.15Compare Source
This release accidentally didn't contain anything.
v7.6.14Compare Source
trueargs in URL getting ignored - #25950, thanks @JReinhold!v7.6.13Compare Source
v7.6.12Compare Source
upgradedetecting the wrong version of existing Storybooks - #25752, thanks @JReinhold!v7.6.11Compare Source
v7.6.10Compare Source
upgrade- #25642, thanks @JReinhold!v7.6.9Compare Source
init,upgradeandsandbox- #25526, thanks @ndelangen, @jreinhold!v7.6.8Compare Source
v7.6.7Compare Source
v7.6.6Compare Source
v7.6.5Compare Source
$appmodules - #25132, thanks @paoloricciuti!v7.6.4Compare Source
v7.6.3Compare Source
v7.6.2Compare Source
v7.6.1Compare Source
v7.6.0Compare Source
Storybook 7.6 is here with increased performance and much more!
List of all updates
@storybook/core-events/preview-errorsdependency missing for Yarn PnP - #24973, thanks @JReinhold!reactand Storybook packagesdevDependencieswhere possible - #24676, thanks @JReinhold!reactand Storybook packagesdevDependencieswhere possible - ATTEMPT 2 - #24834, thanks @JReinhold!addon-onboardingwhen checking versions - #24634, thanks @JReinhold!useStoryPreparedhook failing withundefineddata - #22631, thanks @SpookyJelly!ofprop toPrimaryblock - #23849, thanks @Wilson2k!defaultPropsinStoriesblock - #24506, thanks @WouterK12!store.settings.lastTrackedStoryId- #24115, thanks @rashidshamloo!"type": "commonjs"compatibility - #24534, thanks @ndelangen!react-docgento v7 - #24530, thanks @shilman!SlotDecoratorcomponent - #24800, thanks @JReinhold!goto,invalidateandinvalidateAll- #24955, thanks @paoloricciuti!--testCLI-flag - #24862, thanks @ndelangen!--testistrue- #24799, thanks @ndelangen!@storybook/blocksifbuild.test.emptyBlocksistrue- #24650, thanks @ndelangen!Configuration
📅 Schedule: Branch creation - "" (UTC), 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.
This PR was generated by Mend Renovate. View the repository job log.