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

refactor(dependencies): Move webrick to be a pure development dependency. #322

Merged

Conversation

trammel
Copy link

@trammel trammel commented Sep 24, 2024

Webrick was originally part of the pact application, but is now purely used to support testing.

Also, to quote Jeremy Evans ruby/webrick#145 (comment)

Webrick has not been part of Ruby since the release of Ruby 3.0, over three years ago. While this repository is under the ruby organization on GitHub, it is no longer considered part of Ruby.

Webrick should not be used in production. It is only still maintained because there are other gems relying it, most of which do so only for testing, and only because it is a pure ruby implementation and it was shipped with Ruby in the past.

As Webrick has recently seen a number of CVEs, pulling Webrick in to other codebases unecessarily causes security related maintenance.

It's still fine for testing.

…ncy.

Webrick was originally part of the pact application, but is now purely used to support testing.

Also, to quote Jeremy Evans ruby/webrick#145 (comment)

> Webrick has not been part of Ruby since the release of Ruby 3.0, over three years ago. While this repository is under the ruby organization on GitHub, it is no longer considered part of Ruby.
>
> Webrick should not be used in production. It is only still maintained because there are other gems relying it, most of which do so only for testing, and only because it is a pure ruby implementation and it was shipped with Ruby in the past.

As Webrick has recently seen a number of CVEs, pulling Webrick in to other codebases unecessarily causes security related maintenance.

It's still fine for testing.
@YOU54F
Copy link
Member

YOU54F commented Sep 25, 2024

makes sense Jonathon, cheers for the PR and reference link

@YOU54F
Copy link
Member

YOU54F commented Sep 25, 2024

Pretty sure webrick will still be pulled in however,

pact-ruby requires pact_mock-service here

webrick is a runtime dep in pact_mock-service here and used in a few places (search)

@trammel
Copy link
Author

trammel commented Sep 25, 2024

Oh well. It probably won't make much of a difference immediately, but if pact_mock-service ever switches to an alternative, then there's a little less cleanup in the future here.

Thanks for triple-checking the PR 😁

@YOU54F YOU54F merged commit 1aafba0 into pact-foundation:master Sep 26, 2024
31 checks passed
@YOU54F
Copy link
Member

YOU54F commented Sep 26, 2024

Agreed! Hopefully we may be able to, especially as we move towards leveraging the FFI for the rust based core.

What is the go to replacement for webrick these days? Might be worth adding an issue to track its removal over in pact_mock-service

Thanks for triple-checking the PR 😁

Pleasure dude!

@YOU54F
Copy link
Member

YOU54F commented Sep 26, 2024

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.

3 participants