Bump django-allauth from 0.54.0 to 64.2.1 in /{{cookiecutter.repo_name}}

[dependabot]

Bumps django-allauth from 0.54.0 to 64.2.1.

Changelog

Sourced from django-allauth's changelog.

64.2.1 (2024-09-05)

---

Fixes

• Verifying the email address by clicking on the link would no longer log you in, even in case of ACCOUNT_LOGIN_ON_EMAIL_CONFIRMATION = True.

Security notice

• It was already the case that you could not enable TOTP 2FA if your account had unverified email addresses. This is necessary to stop a user from claiming email addresses and locking other users out. This safety check is now added to WebAuthn security keys as well.

• In case a user signs in into an account using social account email authentication (SOCIALACCOUNT_EMAIL_AUTHENTICATION) and the email used is not verified, the password of the account is now wiped (made unusable) to prevent the person that created the account (without verifying it) from signing in.

64.2.0 (2024-08-30)

---

Note worthy changes

• Verifying email addresses by means of a code (instead of a link) is now supported. See settings.ACCOUNT_EMAIL_VERIFICATION_BY_CODE_ENABLED.

• Added support for requiring logging in by code, so that every user logging in is required to input a login confirmation code sent by email. See settings.ACCOUNT_LOGIN_BY_CODE_REQUIRED.

Security notice

• In case an ID token is used for authentication, the JTI is now respected to prevent the possibility of replays instead of solely relying on the expiration time.

64.1.0 (2024-08-15)

---

... (truncated)

Commits

• 57154de chore: Release 64.2.1
• a7a3a16 fix(mfa): Missing init
• 5c48f11 tests(account): Redirect URL on email verification
• 20e559b fix(socialaccount): Wipe password on email authentication
• 440954f fix(mfa): Prevent add when email unverified
• 6b731eb fix(account): Login on verification broken
• e224199 chore: Opening 64.2.1-dev
• 87edc03 chore: Release 64.2.0
• 1d7f9e9 chore(i18n): Sync .po
• 58ba217 chore(i18n): Sync weblate
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #972.