-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Update puma registration for latest master #2530
Conversation
We're finalizing Puma 6.0, whatever's on Puma master will be what makes it in, so you can finalize this now 👍 |
551d9bf
to
de2f221
Compare
Without this fix, we're blocked from upgrading puma. Any chance of a release? Thanks! |
@amiel options
Pick one, posting on closed issues helps nobody |
Hi @twalpole. As I re-read my comment, I see how it was perceived as impatience, which I apologize for. I did not intend this, but here we are. I will for sure wait and look forward to a release that includes this change. FWIW, I appreciate your time and effort maintaining cabybara, from which I have made use of across many projects over the years. Thank you! |
The capybara gem is currently not compatible with Puma 6 and thus this gem update can't go ahead. Capybara already has a fix for this which hasn't been released [1], I'm hoping that this is a sub-dependency it'll just be updated soon and not be of concern. I'm hoping to avoid a pin as we don't have a direct dependency on puma currently. [1]: teamcapybara/capybara#2530
The capybara gem is currently not compatible with Puma 6 and thus this gem update can't go ahead. Capybara already has a fix for this which hasn't been released [1], I'm hoping that this is a sub-dependency it'll just be updated soon and not be of concern. I'm hoping to avoid a pin as we don't have a direct dependency on puma currently. [1]: teamcapybara/capybara#2530
The capybara gem is currently not compatible with Puma 6 and thus this gem update can't go ahead. Capybara already has a fix for this which hasn't been released [1], I'm hoping that this is a sub-dependency it'll just be updated soon and not be of concern. I'm hoping to avoid a pin as we don't have a direct dependency on puma currently. [1]: teamcapybara/capybara#2530
The capybara gem is currently not compatible with Puma 6 and thus this gem update can't go ahead. Capybara already has a fix for this which hasn't been released [1], I'm hoping that this is a sub-dependency it'll just be updated soon and not be of concern. I'm hoping to avoid a pin as we don't have a direct dependency on puma currently. [1]: teamcapybara/capybara#2530
The capybara gem is currently not compatible with Puma 6 and thus this gem update can't go ahead. Capybara already has a fix for this which hasn't been released [1], I'm hoping that this is a sub-dependency it'll just be updated soon and not be of concern. I'm hoping to avoid a pin as we don't have a direct dependency on puma currently. [1]: teamcapybara/capybara#2530
The capybara gem is currently not compatible with Puma 6 and thus this gem update can't go ahead. Capybara already has a fix for this which hasn't been released [1], I'm hoping that this is a sub-dependency it'll just be updated soon and not be of concern. I'm hoping to avoid a pin as we don't have a direct dependency on puma currently. [1]: teamcapybara/capybara#2530
The capybara gem is currently not compatible with Puma 6 and thus this gem update can't go ahead. Capybara already has a fix for this which hasn't been released [1], I'm hoping that this is a sub-dependency it'll just be updated soon and not be of concern. I'm hoping to avoid a pin as we don't have a direct dependency on puma currently. [1]: teamcapybara/capybara#2530
The capybara gem is currently not compatible with Puma 6 and thus this gem update can't go ahead. Capybara already has a fix for this which hasn't been released [1], I'm hoping that this is a sub-dependency it'll just be updated soon and not be of concern. I'm hoping to avoid a pin as we don't have a direct dependency on puma currently. [1]: teamcapybara/capybara#2530
The capybara gem is currently not compatible with Puma 6 and thus this gem update can't go ahead. Capybara already has a fix for this which hasn't been released [1], I'm hoping that this is a sub-dependency it'll just be updated soon and not be of concern. I'm hoping to avoid a pin as we don't have a direct dependency on puma currently. [1]: teamcapybara/capybara#2530
The capybara gem is currently not compatible with Puma 6 and thus this gem update can't go ahead. Capybara already has a fix for this which hasn't been released [1] [1]: teamcapybara/capybara#2530
The capybara gem is currently not compatible with Puma 6 and thus this gem update can't go ahead. Capybara already has a fix for this which hasn't been released [1] [1]: teamcapybara/capybara#2530
The capybara gem is currently not compatible with Puma 6 and thus this gem update can't go ahead. Capybara already has a fix for this which hasn't been released [1] [1]: teamcapybara/capybara#2530
3.38.0 has been released |
This allows us to move to the latest version of Puma [1]. [1]: teamcapybara/capybara#2530
Capybara 3.38.0 This allows us to move to the latest version of Puma [1]. [1]: teamcapybara/capybara#2530
This is a [major update] of arguably the most important part of our application (the webserver), so proceed with caution! [major update]: https://github.com/puma/puma/releases/tag/v6.0.0 It looks like the only breaking change that impacted us was the one that broke Capybara. This has since been [resolved] and [released]. [resolved]: teamcapybara/capybara#2530 [released]: https://github.com/teamcapybara/capybara/releases/tag/3.38.0 CI is green, but theres no place quite like production. This change should be sanity checked in UAT and Staging environments, and monitored in Production.
This is a [major update][major update] of arguably the most important part of our application (the webserver), so proceed with caution! [major update]: https://github.com/puma/puma/releases/tag/v6.0.0 It looks like the only breaking change that impacted us was the one that broke Capybara. This has since been [resolved][resolved] and [released][released]. [resolved]: teamcapybara/capybara#2530 [released]: https://github.com/teamcapybara/capybara/releases/tag/3.38.0 CI is green, but theres no place quite like production. This change should be sanity checked in UAT and Staging environments, and monitored in Production.
This is a [major update](https://github.com/puma/puma/releases/tag/v6.0.0) of arguably the most important part of our application (the webserver), so proceed with caution! It looks like the only breaking change that impacted us was the one that broke Capybara. This has since been [resolved](teamcapybara/capybara#2530) and [released](https://github.com/teamcapybara/capybara/releases/tag/3.38.0). CI is green, but theres no place quite like production. This change should be sanity checked in UAT and Staging environments, and monitored in Production.
* Bump puma to 6.4.0 * Bump Capybara to 3.39.2 to resolve puma issues in CI teamcapybara/capybara#2530 teamcapybara/capybara@3.37.1...3.39.2 --------- Co-authored-by: Camille Villa <[email protected]>
This is a WIP -- waiting to see what other changes are made to Puma