-
Notifications
You must be signed in to change notification settings - Fork 277
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
Bump https-proxy-agent from 5.0.1
to 7.0.1
(or later)
#5057
Comments
Waiting for upstream bug fix before re-upgrading. |
Hopefully not too far off. TooTallNate/proxy-agents#212 |
The fix has been released in https://github.com/TooTallNate/proxy-agents/releases/tag/https-proxy-agent%407.0.1 a week ago, and is available from npm at https://www.npmjs.com/package/https-proxy-agent/v/7.0.1. Why is there no dependabot PR to bump it again? Since we needed to apply additional changes anyways (see e21c9c2), maybe we should just bump manually. But we still need to understand why we are not getting notified automatically: I do see PRs from the weekly npm check, and no exceptions for this package in |
This is being tracked in #5178. This ticket here is purely about bumping |
5.0.1
to a newer release5.0.1
to a newer release
5.0.1
to a newer release5.0.1
to 7.0.1 (or later)
5.0.1
to 7.0.1 (or later)5.0.1
to 7.0.1
(or later)
In
1.9
we bumpedproxy-agent
from5.0.1
to6.1.0
and that caused some unhandled exceptions on the startup as reported by @byjrack, more details here. This turns out to be a bug with the upstream code and requires a PR to address the issue. I'm creating this issue to keep track of the progress on the PR prior to bumping theproxy-agent
again.The text was updated successfully, but these errors were encountered: