django-allauth 0.26.0 released

Posted by Raymond Penners on 2016-07-24

Note worthy changes

New providers: Weixin, Battle.net, Asana, Eve Online, 23andMe, Slack
Django's password validation mechanism (see AUTH_PASSWORD_VALIDATORS) is now used to validate passwords.
By default, email confirmations are no longer stored in the database. Instead, the email confirmation mail contains an HMAC based key identifying the email address to confirm. The verification lookup includes a fallback to the previous strategy so that there is no negative impact on pending verification emails.
A new setting ACCOUNT_SIGNUP_EMAIL_ENTER_TWICE was added, requiring users to input their email address twice. The setting ACCOUNT_SIGNUP_PASSWORD_VERIFICATION has been renamed to ACCOUNT_SIGNUP_PASSWORD_ENTER_TWICE.
New translations: Latvian, Kyrgyz.

Dropped support for Django 1.6
In order to accommodate for Django's password validation, the clean_password method of the adapter now takes an (optional) user parameter as its second argument.
The new HMAC based keys may contain colons. If you have forked account/urls.py, be sure to sync the account_confirm_email pattern.