lock event-stream to non-compromised version 3.3.4 - Prod unaffected // Test/Dev Security Fix #222
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
phillipperalez
changed the title
wilg
suggested changes
Nov 26, 2018
…e the flatmap change
phillipperalez
changed the title
phillipperalez
changed the title
wilg
approved these changes
Nov 26, 2018
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.
from: dominictarr/event-stream#115
Dependency libraries should have already updated this but let's make sure that the version is at a non-compromised version explicitly. This did not affect production as this is a
nodemonvulnerability. We do not run nodemon for prod, only for test/dev commands.