fix: Update js-yaml v4.3.0 -> v4.3.1 to resolve high security issue - #6144
Closed
OIRNOIR wants to merge 1 commit into
Closed
fix: Update js-yaml v4.3.0 -> v4.3.1 to resolve high security issue#6144OIRNOIR wants to merge 1 commit into
OIRNOIR wants to merge 1 commit into
Conversation
|
|
Owner
|
Thanks for the report. $ npm install pm2@7.0.4 -g
$ pm2 update |
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
3 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.
npm auditshows a high severity vulnerability injs-yamlv4.3.0. A new versionv4.3.1was released last week to fix this vulnerability. The fixing commit can be viewed here: nodeca/js-yaml@c3cc4b0