Upgrade debug module because of Vulnerability #4533 #4544
Closed
Conversation
This file contains 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
Signed-off-by: Outsider <outsideris@gmail.com>
outsideris
added
type: chore
|
closed by #4556 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of the Change
debug@4.20 has a low-severity ReDos regression, and it fixed in 4.3.1.
A deprecation warning is printed when users install mocha.
Our nested dependencies has debug@4.1.1. But they are
devDependencies.Why should this be in core?
I think Mocha isn't vulnerable to it.
But we don't want users to see this kind of security warnings.
Applicable issues
Fix #4533