-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Protect users from high risk vulnerability with a new release version #256
Comments
Yes, please, a new release. My workaround at the moment is to include the latest in package.json as:
|
I agree, a new release would make sense and protect users of this package. |
silverbackdan
changed the title
New release?
Protect users from high risk vulnerability with a new release version
Aug 11, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The patches applied in October / November last year could do with being released to prevent a high risk vulnerability in url-parse and so we are able to upgrade without rebuilding the package in our own fork. Would it be possible to make a new release?
The text was updated successfully, but these errors were encountered: