-
Notifications
You must be signed in to change notification settings - Fork 375
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
fix rack 3/rackup situation on ruby 3.4 #4068
Conversation
The ruby 3.3 failure is being repaired as part of 2.5.0 release process, after 2.5.0 goes out merging master into this PR should make that configuration green. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4068 +/- ##
=======================================
Coverage 97.72% 97.73%
=======================================
Files 1338 1338
Lines 80248 80248
Branches 4016 4016
=======================================
+ Hits 78424 78427 +3
+ Misses 1824 1821 -3 ☔ View full report in Codecov by Sentry. |
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.
Good find. Thank you!
rack 3.1.0 deletes Rack::VERSION constant (in rack/rack#1966), causing our tests to fail. Use Rack::RELEASE instead of Rack::VERSION to work around the issue
What does this PR do?
rack 3.1.0 deletes Rack::VERSION constant (in
rack/rack#1966),
causing our tests to fail.
Use Rack::RELEASE instead of Rack::VERSION
to work around the issue
Motivation:
Repairing CI in #4040
Change log entry
None, changes are in test suite only.
Additional Notes:
How to test the change?
I am assuming currently the tests lock rack to pre-3.1.0 therefore there aren't any failures on master, however #4059 exposed this failure when trying to get a new ruby 3.4 configuration going in circleci.