-
Notifications
You must be signed in to change notification settings - Fork 18
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
Support for Puma 6.0 #25
Conversation
Hey @Envek let me know if this works or if you'd like a different direction |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey, thanks for the pull request!
In general it should work, yes. However, I wonder, whether it worth the effort to support all Puma version at once. We can just stick with Puma 6 only, I think. Users of older Puma versions always can use older yabeda-puma-plugin versions.
@Envek I'll update the code to only work for Puma 6 |
This reverts commit de877a6.
Hm, no idea what is wrong with specs… Most probably some dependencies broke tests, because even current master started to fail with that |
@skryukov, thanks a lot! |
@Envek thanks for merging, think we could get a new gem cut too? Thanks |
Thank you for the pull request! Released in 0.7.0 |
Puma 6 introduced some small breaking changes to the Puma::Server API, seemed easier to handle these without pattern matching the puma version string.