Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Security] Bump lodash from 4.17.11 to 4.17.15 #8351

Merged
merged 1 commit into from Oct 14, 2019

Conversation

NMinhNguyen
Copy link
Contributor

@NMinhNguyen NMinhNguyen commented Oct 8, 2019

See https://www.npmjs.com/advisories/1065

Issue:

What I did

Updated to the latest published Lodash version. I could've just bumped to ^4.17.12 as per the advisory, but figured I might as well use the latest version. Although ^4.17.11 does allow the installation of newer non-vulnerable versions, 4.17.11 satisfies that version range and seems to cause Snyk to produce warnings.

How to test

  • Is this testable with Jest or Chromatic screenshots? No
  • Does this need a new example in the kitchen sink apps? No
  • Does this need an update to the documentation? No

If your answer is yes to any of these, please make sure to include it in your PR.

@vercel
Copy link

vercel bot commented Oct 8, 2019

This pull request is automatically deployed with Now.
To access deployments, click Details below or on the icon next to each push.

Latest deployment for this branch: https://monorepo-git-fork-nminhnguyen-lodash.storybook.now.sh

@NMinhNguyen
Copy link
Contributor Author

NMinhNguyen commented Oct 9, 2019

@shilman there's some build failures but I'm guessing they're unrelated? Btw the motivation for this change is I was tryna onboard Storybook to our private npm registry at work, but it leverages Snyk for vulnerability scanning and it rejected my request due to lodash.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies patch:done Patch/release PRs already cherry-picked to main/release branch patch:yes Bugfix & documentation PR that need to be picked to main branch security
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants