Closed JunichiIto closed 6 years ago
I'm going to see what I can do about this without a major overhaul. I've always tried to avoid locking people into a specific version of Ruby, so I'm going to try upgrading Devise first. If that doesn't work, I'll fall back to a specific Ruby.
To clarify, I try to handle supported versions of Ruby ... so I'd like this to work with Ruby 2.3 or newer, at least. Maybe I should set up CI to build across multiple Rubies.
I think "CI to build across multiple Rubies" is good solution 👍
I was able to update Devise and test manually in Ruby 2.4 and Ruby 2.5. Aside from merge conflicts in Gemfile.lock from chapter to chapter, there were no issues.
I will push this up in the next few days when I release an updated version of the book.
I released a version that uses the updated Devise. I'm working on CI builds across multiple Rubies as a separate project.
When I ran the specs in this repository against Ruby 2.5.1, I got the following error:
This error is related to this issue.
I think some of these actions are required:
.ruby-version
file to fix Ruby version for rbenv users.