Update request dependency to current version #200
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
Previous version has a known security vulnerability: https://nodesecurity.io/advisories/309
|
Thanks for the critical update! |
|
My pleasure! Do you think you can publish a release to npm sometime soon? |
nfriedly
added a commit
to watson-developer-cloud/node-sdk
that referenced
this pull request
May 19, 2017
to get lbdremy/solr-node-client#200 which resolves node security issue fixes #456 [semver patch]
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.
Previous version has a known security vulnerability: https://nodesecurity.io/advisories/309
This in turn causes Node Security Platform's checks to fail for anything that depends on solr-client (example)