Closed nguyenngoc2505 closed 2 years ago
Ahh, I think the problem here is the endless range which isn't in Ruby 2.5, I introduced code linting which changed the formatting. Also, I dropped 2.5 from the test suite as that ruby version is now EOL. I'll update the gem requirements so this doesn't happen in the future (you would be blocked from installing on 2.5).
In the short term, you can use an older version of the gem (1.x should still work with Ruby 2.5) until you can update your app to a non-EOL ruby version (3.x, 2.7.x, 2.6.x are currently supported by Ruby core). Ruby 2.5 was EOL in April https://www.ruby-lang.org/en/news/2021/04/05/ruby-2-5-9-released/
After this release, Ruby 2.5 reaches EOL. In other words, this is the last release of Ruby 2.5 series. We will not release Ruby 2.5.10 even if a security vulnerability is found. We recommend all Ruby 2.5 users to upgrade to Ruby 3.0, 2.7 or 2.6 immediately.
Also, I can investigate bringing back support for 2.5 for at least one major release cycle. Otherwise, the versioning resolution won't work itself out (since 2.x isn't properly tagged with a ruby version requirement).
And...i'll have to couple it to the derailed support version. I think i'll backport 2.5 support for sure then. Sorry about that.
Should be fixed gem install dead_end && bundle update dead_end
sorry about that https://github.com/zombocom/dead_end/pull/90
Hi, I've problem with dead_end
Any ideas how to solve this? Maybe this error from new release dead_end version?