Closed j0sh3rs closed 6 months ago
I've opened a small PR to drop support for Ruby 2.x: https://github.com/ruby-i18n/i18n/pull/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 racc
required CMake extensions to run, and agree this shouldn't have been in the point release.
Historically, people get grumpy when I yank versions, typically because their Gemfile.lock
says one thing, but RubyGems.org says another. I know I get grumpy when it happens to me, too.
So I think the way to make people happy here is to undo the racc
dependency in 1.14.x. This would then allow most people to gem install i18n '~> 1.1'
and it to succeed still.
Then, we can re-apply that in a v2, and fix the Ruby version to boot.
@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
@radar
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! :heart: