forked from heartcombo/devise
-
Notifications
You must be signed in to change notification settings - Fork 4
How to: upgrade to devise 2.1
josevalim edited this page May 29, 2012
·
13 revisions
If you run your application with Devise 2.0 and have solved all the deprecations, you're good to go with Devise 2.1. If you are not on Devise 2.0, migrate first to 2.0 before running on 2.1.
If you're using encryptable on your models, you will now have to include devise-encryptable
on your gemfile.
Now the sign_out
through JSON or XML returns a contentless response instead of a response with an empty body.