-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Update package-json
to >=8.0.0 for vulnerability in got
>= 12.0.0, < 12.1.0, < 11.8.5
#2028
Comments
Duplicate of: #2023 |
Releasing now. |
I am not sure this was resolved. When I install the latest nodemon, and then run an audit, I get the following results...
Perhaps I did not update nodemon correctly? Thanks! |
@kevinswarner Can you show me your package.json and package-lock.json files? I can setup a project with these files on my computer and check if I get the same error. |
Had to revert, it borked people's install. |
Here are my deps and dev deps. I deleted my lock file and reinstalled, but got the same result.
|
Okay, so we now have v2.0.17 that uses the new update-notifier, but v2.0.18 reverted this change, because v2.0.17 broke people's install. But that means v2.0.18 still has the vulnerability. So... how is this going to be fixed? |
You need to use v2.0.17, read my last comment. It seems there are some issues with bumping update-notifier to the new version, so let's just wait for a fix. |
By reading issue #2031 we can see that due to issues with update-notifier the project owner plans to drop this dependency entirely in the next release. So, hopefully, this will get fixed in the next release. Until then, I recommend using v2.0.17 if it doesn't break your install, and otherwise use v2.0.18 or v2.0.16. |
Closes #1961 Closes #2028 - Fixes security issue with got (CVE-2022-33987) - Replace update-notifier with simple-update-notifier which does the same thing but has one dependency (semver) rather than several - Same caching settings as update-notifier Congratulations and thanks to @alexbrazier 👏 🥇 ❤️
🎉 This issue has been resolved in version 2.0.19 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Dependabot flagged a security issue with one of nodemon's dependencies. That issue is resolved in 2.0.19 as discussed in the nodemon repo[1]. [1] remy/nodemon#2028
Environment
nodemon -v
: 2.0.15node -v
: v14.18.1Issue
Possible fix
package-json
to >=8.0.0 as it points to fixed dependency forgot
>12.1.0The text was updated successfully, but these errors were encountered: