-
Notifications
You must be signed in to change notification settings - Fork 598
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
CI: test Padrino with Sinatra v3+ after it is known to be compatible #1466
Milestone
Comments
NOTE: Padrino development is considered to be halted. |
Filed padrino-framework#2258 |
Closing until Padrino lives again |
The padrino-framework#2258 issue I filed has been completed. We should be set to test Padrino with Sinatra 3+ after a new version of Padrino (newer than 0.15.1) is released. |
Work has been completed on this issue. |
I've now deployed 0.15.2 with the fixes |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With #1465 we had to lock Sinatra to < 3 for our Padrino tests, as Padrino seems to want to modify the
CALLERS_TO_IGNORE
array which is now frozen with Sinatra 3.0.0.After Padrino releases a new version of padrino-core beyond the current 0.15.1 version, we should check to see if we are able to revert the change that #1465 delivered. NOTE that a new version of padrino-core need not specifically solve the Sinatra v3.0.0 compatibility problem. It could also simply add a dependency on Sinatra < 3 so that we no longer have to do so manually.
The text was updated successfully, but these errors were encountered: