chore(deps): update dependencies with CVEs - #3223
Merged
oxy merged 1 commit intoApr 26, 2021
Merged
Conversation
Copy link
Copy Markdown
Sorry, something went wrong.
Copy link
Copy Markdown
Codecov Report
@@ Coverage Diff @@
## main #3223 +/- ##
=======================================
Coverage ? 46.81%
=======================================
Files ? 23
Lines ? 1194
Branches ? 237
=======================================
Hits ? 559
Misses ? 451
Partials ? 184 Continue to review full report at Codecov.
|
Sorry, something went wrong.
jsjoeio
approved these changes
Apr 26, 2021
jsjoeio
left a comment
Copy link
Copy Markdown
Contributor
There was a problem hiding this comment.
Thanks for taking care of these 🙌
Sorry, something went wrong.
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
Reviewers
1 more reviewer2 participants
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.
Update devDependencies with known CVEs.
They only process trusted data, so there is no need for us to release a security advisory; but cherry-pick updates for them nonetheless to satisfy tools like Trivy.