django-allauth 64.0.0 released
Posted by Raymond Penners on 2024-07-31
Note worthy changes
- The 0.x.y version numbers really did not do justice to the state of the project, and we are way past the point where a version 1.0 would be applicable. Additionally, 64 is a nice round number. Therefore, the version numbering is changed from 0.x.y to x.y.z. We will use a loose form of semantic versioning. However, please be aware that feature releases may occasionally include minor documented backwards incompatibilities. Always read the release notes before upgrading.
- Added support for WebAuthn based security keys and passkey login. Note that this is currently disabled by default.
- Headless: The TOTP URI is now available in the MFA activation response.
- Headless: When trying to sign up while a user is already logged in, you now get a 409.
- Headless: You can now alter the user data payload by overriding the newly introduced serialize_user() adapter method.
- Headless: The token strategy now allows for exposing refresh tokens and any other information you may need (such as e.g. expires_in).
- Ensured that email address, given name and family name fields are stored in the SocialAccount instance. This information was not previously saved in Amazon Cognito, Edmodo, and MediaWiki SocialAccount instances.
- When multiple third-party accounts of the same provider were connected, the third-party account connections overview did not always provide a clear recognizable distinction between those accounts. Now, the SocialAccount.__str__() has been altered to return the unique username or email address, rather than a non-unique display name.
Backwards incompatible changes
- Dropped support for Django 3.2, 4.0 and 4.1 (which all reached end of life). As Django 3.2 was the last to support Python 3.7, support for Python 3.7 is now dropped as well.
Next: django-allauth 64.1.0 released Previous: django-allauth 0.63.6 released