Merge devise-4 branch into master and release v3.0.0 about devise-two-factor HOT 5 CLOSED

Apologies for being a nuisance, but I figure someone has to be :P

I'll be testing the devise-4 branch with GitLab (along with Devise 4/attr_encrypted 3.0) in the next few days. Assuming nothing breaks horribly, it should be good to merge.

Rails 5.0.0.rc1 came out today, so I figured it was important to get this shipped: https://github.com/rails/rails/releases/tag/v5.0.0.rc1

If there's anything else I can do to get this moving along, I'd be happy to help.

from devise-two-factor.

Maybe also allow rotp 3.0 in the gemspec?

Here's the breaking change introduced in that version.

from devise-two-factor.

pokes @bsedat 😛

from devise-two-factor.

Alternatively @ShaneWilton, I'd like to upgrade to Devise 4 if possible :)

from devise-two-factor.

Other than #91 (and merging #90), devise-two-factor (with devise-4 merged into master) seems to be working fine based on my tests with GitLab :)

from devise-two-factor.