Bump django-allauth from 0.54.0 to 0.57.0

[dependabot]

Bumps django-allauth from 0.54.0 to 0.57.0.

Changelog

Sourced from django-allauth's changelog.

0.57.0 (2023-09-24)

---

Note worthy changes

• Added Django password validation help text to password1 on set/change/signup forms.

• Microsoft: the tenant parameter can now be configured per app.

• SAML: Added support for additional configuration parameters, such as contacts, and support for certificate rotation.

• The enumeration prevention behavior at signup is now configurable. Whether or not enumeration can be prevented during signup depends on the email verification method. In case of mandatory verification, enumeration can be properly prevented because the case where an email address is already taken is indistinguishable from the case where it is not. However, in case of optional or disabled email verification, enumeration can only be prevented by allowing the signup to go through, resulting in multiple accounts sharing same email address (although only one of the accounts can ever have it verified). When enumeration is set to True, email address uniqueness takes precedence over enumeration prevention, and the issue of multiple accounts having the same email address will be avoided, thus leaking information. Set it to "strict" to allow for signups to go through.

Fixes

• Fixed ?next= URL handling in the SAML provider.

• During 2FA, pending logins were incorrectly removed when e.g. Django was asked to serve a /favicon.ico URL.

0.56.1 (2023-09-08)

---

Security notice

• ImmediateHttpResponse exceptions were not handled properly when raised inside adapter.pre_login(). If you relied on aborting the login using this mechanism, that would not work. Most notably, django-allauth-2fa uses this approach, resulting in 2FA not being triggered.

0.56.0 (2023-09-07)

... (truncated)

Commits

• 701ef63 chore: Release 0.57.0
• abb7383 tests: Undo coverage config change
• 611360d tests: Small coverage related improvements
• 72e2718 feat(account): Strict enumeration prevention vs add email
• ddadb93 feat(account): Added prefilling of email field in signup form
• f98c9a3 fix(socialaccount): Yank dupe email during auto signup failure
• aaa0b67 docs(openid): refactor structures
• 3851449 fix(socialaccount): Handle UUID user.pk
• be779df fix(socialaccount): Fetch settings from main provider
• 24049ad fix(openid): Populate provider ID
• 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)