My current problem is that many gems are not publishing their required_ruby_version.
This means that a Gemfile/gemspec must know what is the maximum version of a gem for a given version of Ruby, instead of bundler figuring it out for us.
It takes about one minute for the gem author to add the line. When the author doesn't, everyone that uses the gem, directly or indirectly, may have to figure out the maximum version and specify it in their own gemfiles.
Note that there is currently no good way to correct this mistake. Once it is done, the only option is to yank the gem which is typically not what one wants to do.
required_ruby_version is currently in the "Optional" section of the spec. It's not even in the "Recommended" section!
It should be mandatory and enforced.
My current problem is that many gems are not publishing their
required_ruby_version.This means that a Gemfile/gemspec must know what is the maximum version of a gem for a given version of Ruby, instead of bundler figuring it out for us.
It takes about one minute for the gem author to add the line. When the author doesn't, everyone that uses the gem, directly or indirectly, may have to figure out the maximum version and specify it in their own gemfiles.
Note that there is currently no good way to correct this mistake. Once it is done, the only option is to yank the gem which is typically not what one wants to do.
required_ruby_versionis currently in the "Optional" section of the spec. It's not even in the "Recommended" section!It should be mandatory and enforced.