-
-
Notifications
You must be signed in to change notification settings - Fork 16.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
In-place Express update to 4.15.5 still has old forwarded #3432
Comments
The semver range already covers the patched version. Simply upgrading to 4.15.5 will force the new version of the dependency. |
The plan is to include proxy-addr 2.0.2 in Express.js 4.16 on Monday Oct 2, but until then installing a fresh Express.js 4.15.5 will drop you forwarded 0.1.2 in your tree. |
If it helps, here is what the
Let me know if there is still something you need or if there is something preventing you from picking up the correct version of |
Ok, so I've been experimenting a bit, and definitely with npm@5 getting a simple command to bump I think that even if this causes the "mime" fixed to be delayed, juggling around the dependencies more and getting an Express 4.15.6 that have all semver ranges to not allow |
This certainly will make me think about bothering with semver ranges at all any more. Having ranges instead of a specific version adds risk to the install, but it's generally been argued that the trade off of getting security updates is worth it. This seems to indicate that it really only helps users who don't already have it installed, and the existing user base cannot take advantage of it as easily :( |
Yes, that is an interesting paradox. Thank you so much for your help. |
Express.js 4.16.0 is out now where the |
Hello, I'm writing to request an update for the dependency proxy-addr to a version, like version 2.0.2, that has the security patched version of forwarded in it's dependencies., 0.1.2.
Thanks!
The text was updated successfully, but these errors were encountered: