updated yargs package to 13.1.0 version #59
Merged
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
|
Hey @MaksPob, thanks for the PR. Can you bump |
MaksPob
force-pushed
the
update-yargs-package-to-13-1
branch
from
a66bc54 to
22a4d6a
Compare
MaksPob
force-pushed
the
update-yargs-package-to-13-1
branch
from
63ebe71 to
f95d421
Compare
Hi @MartynasZilinskas! Ok i did it;))I understood you correctly?)) |
MartynasZilinskas
approved these changes
Apr 8, 2019
|
@MaksPob Thanks. 👍 |
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
There is a vulnerability in yargs package, because its version is old.
https://app.snyk.io/vuln/npm:mem:20180117
What is the new behavior?
I updated the version of the yargs package. Vulnerability should not be.
Does this PR introduce a breaking change?
I'm not sure.
Other information
You are using the old version of the yargs package, which at that time used the old version of the os-local package, which used the vulnerable version of the package mem.
https://app.snyk.io/vuln/npm:mem:20180117
Reviewers
@MartynasZilinskas @DovydasNavickas