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

upgraded lodash version 4.17.15 to 4.17.20 to fix reported issue #337

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Salinn
Copy link

@Salinn Salinn commented Feb 4, 2021

What:

Looking to update lodash from version 4.17.15 to 4.17.20 to fix https://snyk.io/test/npm/lodash/4.17.15

Why:

Upgrade to a version without the know vulnerability

How:

Updating the package.json

Checklist:

  • [N/A] Documentation
  • Tests
  • [N/A] Updated Type Definitions
  • Ready to be merged

I believe this would be ready to be merged and a version bump to occur after being reviewed.

@codecov
Copy link

codecov bot commented Feb 4, 2021

Codecov Report

Merging #337 (b35c2f8) into main (e148894) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##              main      #337   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           23        23           
  Lines          537       537           
  Branches       195       195           
=========================================
  Hits           537       537           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e148894...dfb3898. Read the comment docs.

@pvargas
Copy link

pvargas commented Jan 31, 2022

It should probably be updated to version 4.17.21 instead, since there are known vulnerabilities in version 4.17.20: https://snyk.io/test/npm/lodash/4.17.20

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants