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 3.1.2 contains code that doesn't work on Ruby 2.4 and below #447

Closed
mvz opened this issue Jan 14, 2021 · 5 comments · Fixed by #448
Closed

Version 3.1.2 contains code that doesn't work on Ruby 2.4 and below #447

mvz opened this issue Jan 14, 2021 · 5 comments · Fixed by #448

Comments

@mvz
Copy link
Contributor

mvz commented Jan 14, 2021

This line is not legal in older rubies: https://github.com/feedjira/feedjira/blob/master/lib/feedjira/date_time_utilities/date_time_pattern_parser.rb#L15

Perhaps this setting should be adjusted: https://github.com/feedjira/feedjira/blob/master/.rubocop.yml#L4

Rubocop didn't catch the mismatch with the supported set of Rubies due to this exclusion: https://github.com/feedjira/feedjira/blob/master/.rubocop.yml#L10

@mvz
Copy link
Contributor Author

mvz commented Jan 16, 2021

From #435 I conclude that the intent is to support Ruby 2.5 and up, so simplest fix would probably be to update the required ruby version in the gemspec.

@Ben-Fenner
Copy link

This caught me out today as rubygems.org still lists feedjira version 3.1.2 as compatible with Ruby 2.2. =/

https://rubygems.org/gems/feedjira/versions/3.1.2

@mockdeep
Copy link
Member

@Ben-Fenner yeah, in retrospect we should have had a major version update before deprecating the older Ruby versions. I spent a while just seeing what it would take to add back support for the older Ruby versions, and unfortunately it looks like it would take a lot of work to add support for older versions while also supporting newer ones.

@Ben-Fenner
Copy link

I'd be curious what it would take to get rubygems.org to update their specs. I have no idea how that works though. Do they introspect the code and determine things that way, in which case it would take rewriting git history on your gem to an insane degree to accomplish? Or can rubygems.org be sent an e-mail to update that one and that's all it takes? That would be the solution I'd be looking into anyway.

At the end of the day it worked out for me. Luckily this issue existed for me to research.

@mockdeep
Copy link
Member

@Ben-Fenner RubyGems doesn't allow tampering with a gem version after it is released for the sake of security and reliability. We could yank the gem, but that would break anybody who is currently using that release. For better or worse, I think our best bet is to let this sit and hope that everybody is able to upgrade their Ruby version at some point.

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

Successfully merging a pull request may close this issue.

3 participants