Skip to content
This repository was archived by the owner on May 5, 2023. It is now read-only.

Update https-proxy-agent to fix a vulnerability#47

Merged
TooTallNate merged 2 commits intoTooTallNate:masterfrom
adrukh:patch-1
Oct 15, 2019
Merged

Update https-proxy-agent to fix a vulnerability#47
TooTallNate merged 2 commits intoTooTallNate:masterfrom
adrukh:patch-1

Conversation

@adrukh
Copy link
Copy Markdown
Contributor

@adrukh adrukh commented Oct 9, 2019

See TooTallNate/proxy-agents#77

I took the liberty to bump the version to 3.2.0, let me know if you want to do this on a separate commit.

@TooTallNate
Copy link
Copy Markdown
Owner

The version bump should indeed be a separate commit. Can you remove that part please?

@adrukh
Copy link
Copy Markdown
Contributor Author

adrukh commented Oct 10, 2019

Done!

@adrukh
Copy link
Copy Markdown
Contributor Author

adrukh commented Oct 10, 2019

Kind ask to publish this as a non-breaking change 🙏 Unless you think it is?

@lili2311
Copy link
Copy Markdown

👋 @TooTallNate do you know when this may be merged?

@TooTallNate TooTallNate merged commit 3588645 into TooTallNate:master Oct 15, 2019
@adrukh adrukh deleted the patch-1 branch October 16, 2019 04:47
@lili2311
Copy link
Copy Markdown

👏 ty!

@mkj28
Copy link
Copy Markdown

mkj28 commented Oct 17, 2019

@TooTallNate not sure how it works - but do you know when this will be published to npm?

@sidtagirisa
Copy link
Copy Markdown

@TooTallNate Hi, can you please publish this to npm? now if we install from npm, https-proxy-agent is still 2.2.1, and audit is complaining.

@Wallyworldg02
Copy link
Copy Markdown

See TooTallNate/proxy-agents#77

I took the liberty to bump the version to 3.2.0, let me know if you want to do this on a separate commit.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants