Update merge npm due to high security vulnerability. #4
Conversation
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
dalarson
approved these changes
Mar 2, 2022
|
Bumping this thread - Also dealing with need to mitigate security vulnerability in merge. Can we merge this update? |
|
Hi, can we get a release with this change pushed to npm public registry? |
Bumping this thread. We cannot consume these changes unless a new release is published to public npm registry. Can we please get a release pushed? Thanks in advance. |
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.
Currently ejs-webpack-loader is dependent on a package, merge, with a high security vulnerability. This PR simply updates the merge package to the recommended version.