-
Notifications
You must be signed in to change notification settings - Fork 455
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
1.9 release #399
Comments
Yes! I missed a setting required for rubygems, so it will be 1.9.1. Should have it pushed this week! |
Great thanks @BryanH |
@BryanH Thanks. :) |
Ugh, with TravisCI.org shuttting down, the merge-test-release cycle is VERY slow. Testing is taking 15-20 hours for each merge. I just published 1.9.1 and will request a push to rubygems as soon as it passes TravisCI testing |
Awesome print should probably move to Github Actions, what do you think? 1.9.0 is not available yet on https://rubygems.org/gems/awesome_print/versions |
@guillaumebriday 100% agree, now that TravisCI is shutting down/severely limiting the FOSS tier. |
Good news everyone, we're on track to release 1.9.x to Rubygems. I totally understand the frustration--and share it--and appreciate your hanging in there. |
One of the tests is still failing on Ruby 2.7.x - once that's resolved we'll be good to go |
@BryanH If we can help feel free to ask! 👍 |
@BryanH No pressure here, just curious if there's any way I could help as well; happy to lend a hand if you all need it! Looking forward to the 1.9 release |
@keyboard-clacker @guillaumebriday The ruby-head tests are failing; I marked them ignore for now, but if someone could submit a PR so ruby-head passes, that would be really helpful |
For what it worth, there is a maintained fork here : https://github.com/amazing-print/amazing_print |
According to the changelog : https://github.com/awesome-print/awesome_print/blob/master/CHANGELOG.md#190
The 1.9 has been released but it's not available on rubygems.
Could you release it please?
Thanks 👍
The text was updated successfully, but these errors were encountered: