Closed theflow closed 5 years ago
Agreed, same with AWS Beanstalk. The commit that added doesnt describe any technical reason to have it so high.
@theflow 👋 just merged a depfu PR that broke our deployment due to this.
haml-rails should get a changelog to warn people of such things. looking into the commit-history is not a feasible solution.
travis-ci is also still on an incompatible older version of rubygems.
Same for semaphoreCI
Please do release a relaxed required_rubygems_version.
We are working at our company (i think like many others) with the Ubuntu LTS versions and it's packages. Latest LTS ist 18.04 and it's coming with rubygems version 2.7.6 (2.5.2.1 on 16.04) - so we are actually not able to use haml-rails 2.0.0
Can a developer please comment on this?
We have the same issue with AWS OpsWorks, Chef 11 and Rails 5.
Still impacting Heroku.
Looks like this was fixed in #154 and released in version 2.0.1, tested with Ruby 2.5 / RubyGems 2.7.6 and the install succeeded
Right. Fixed via #154.
Hi,
Would it be possible to relax the
required_rubygems_version
requirement? Given that Heroku still ships Rubygems 2.6 with Ruby 2.4 and Rubygems 2.7 with Ruby 2.5 makes it a bit hard to use this gem there.Cheers, Florian