Skip to content
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

Version 1.8.0. and 1.8.1. pulled from RubyGems, breaking build #357

Closed
filipkis opened this issue Jul 5, 2021 · 1 comment
Closed

Version 1.8.0. and 1.8.1. pulled from RubyGems, breaking build #357

filipkis opened this issue Jul 5, 2021 · 1 comment

Comments

@filipkis
Copy link

filipkis commented Jul 5, 2021

Hi guys,

We just noticed today that version 1.8.0 and 1.8.1 were pulled from RubyGems which suddenly caused all our CI to break. Quickly I couldn't find any obvious mention of critical issues that would cause you to pull the gem. Still if there is, it would still be desired to leave older releases there, but put the disclaimer in the changelog that new ones should be used.

Thanks

@rjherrera
Copy link
Member

Hi there @filipkis! We are very sorry, we didn't handle the last update correctly, as you say we should have left those versions and warned to update to the new ones. We'll make sure it doesn't happen again.

The reason behind the unusual update was that, by mistake, we were including vendor files into the gem, so those versions were around 80MB instead of the usual <1MB. Still, we shouldn't have pulled those versions from RubyGems, sorry for the problems caused. We will update the changelog accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants