Skip to content
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 to https-proxy-agent 7.0.1 and update client code. #5214

Merged
merged 1 commit into from
Jul 24, 2023

Conversation

ericpromislow
Copy link
Contributor

@ericpromislow ericpromislow commented Jul 21, 2023

Fixes #5057

See also #4622 to see how the client code was changed going from 5.x to 6.0

6.0 was a breaking change, so we needed to update the client code. There hasn't been a breaking
change since then, and no client change appears necessary.

References:

5009 - how the 6.x version broke proxies

If someone with all the required network pieces could test this change so it breaks with the 1.9.0 release but works here, that would be great. FWICT the failure happened at startup while collecting certs.

Signed-off-by: Eric Promislow <epromislow@suse.com>
@gaktive gaktive requested a review from rak-phillip July 24, 2023 18:10
Copy link
Contributor

@rak-phillip rak-phillip left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think these changes look good. I trust that the issue, as it was previously identified, was fixed upstream.

@rak-phillip rak-phillip merged commit 0dec7fb into main Jul 24, 2023
@rak-phillip rak-phillip deleted the 5057-bump-to-recent-https-proxy-agent branch July 24, 2023 23:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bump https-proxy-agent from 5.0.1 to 7.0.1 (or later)
2 participants