Not specifying required ruby version on Gemfile causes my bundler with ruby 2.5.x pull dotenv 2.8.0 about dotenv

[bkeepers]

I release 2.8.1 that adds support for 2.5 and 2.6. Y'all really should upgrade to a supported version of Ruby.

[natematykiewicz]

I said basically the same thing here:
d7c9135#commitcomment-79569950

[paul-c-hanson]

We are encountering the same issue on a project for the NHS in the UK. We are pinned to an older version of Ruby at the moment, and the dotenv update has caused an issue in our packaging process. Is there a way to pin the version of dotenv to 2.7.x if the change to the gem file will take some time?

[tevvi]

The same issue for ruby 2.5.8, we used dotenv through dotenv-rails. Fixed by adding it to our Gemfile:

gem 'dotenv-rails', '< 2.8'

[jeff-hiner]

Y'all really should upgrade to a supported version of Ruby.

Tell that to the maintainers of CentOS/RHEL 8. I wouldn't care either as I don't directly use Ruby, but my CI system targets RHEL for one build, and we use fpm which depends on dotenv.

I don't think anyone is arguing that you can't or shouldn't drop support for EOL'd Ruby versions, but if you're going to do so the reasonable and polite thing to do is specify a minimum Ruby version in the manifest so as not to break a bunch of folks' builds.

[0b5vr]

Thank you for the support, while that was not an intended way to close this issue as others mentioned here.