-
-
Notifications
You must be signed in to change notification settings - Fork 411
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
[BUG] Latest Release Required Cmake (building native extensions) #685
Comments
I've opened a small PR to drop support for Ruby 2.x: #686 I would suggest withdrawing v1.14.3, then merge in my PR, and publish a new version (2.x) |
Thanks for taking the time to write all that up. I had planned on handling the Ruby bump in some separate work, but then real life took over. That would indeed be a major version bump change. I hadn't remembered that Historically, people get grumpy when I yank versions, typically because their So I think the way to make people happy here is to undo the Then, we can re-apply that in a v2, and fix the Ruby version to boot. |
This causes people's builds to break. See #685 for the discussion.
@radar Do you have a rough ETA on when you expect this fix to be pushed out? |
@dsgithub81 Today, Australian Eastern Time. The day has just begun. |
Please try out v1.14.4 and let me know how you go. |
Thank you, it is working now! Another question, are you planning to release the v2 soon? Curious how long I will have before the gem install i18n '~> 1.1' is a must have |
What I tried to do
i18n
as a dependency of theactivesupport
gem, which is a dependency of various google cloud gems.i18n
requires cmake to compile the gem on installationWhat I expected to happen
What actually happened
i18n
to v1.14.1Versions of i18n, rails, and anything else you think is necessary
Thanks! ❤️
The text was updated successfully, but these errors were encountered: