3.0.0

What's Changed

• Drop custom separator in favor of default colon (:) by @amureki in #28

Dot is unreserved character, however the representation in browsers (%2E or .), mail clients and even SMTP-servers is not unified and can lead to different issues.

Please, note: after installing this new release, existing authentication links will become invalid.
If you want to keep the old dot separator, you wound need to customize MailAuthBackend, but this is not advisable.

New Contributors

• @amureki made their first contribution in #28

Full Changelog: 2.1.3...3.0.0

2.1.3

• Fix next URL encoding
• Update CI suite
• Update supported Python and Django versions
• Fix Django 4.0 deprecation warnings
• Add tests to source dist

2.1.2

• Log a warning if inactive user tries to authenticate #20
• Reformat code to match black code style
• Fix docs build

2.1.1

• Resolve Django 4.0 deprecation warnings

2.1.0

• Add Django 3.1 support
• Add _legacy_get_session_auth_hash to fix Django 3.1 support #18

2.0.0

Switch token separate from / (slash) to URL safe character . (dot)

Some email clients replace double slashes with a single slash.
The double slash occurred for users with no last_login date (newly
created users).

To bypass this issue, the separator is changed to . (dot) as it is
a non-reserved URL safe character (RFC3986 2.3) and not part of the
base64url alphabet.

See also:
https://www.ietf.org/rfc/rfc3986.txt
https://tools.ietf.org/html/rfc4648

1.0.3

• Add more verbose logging to MailAuthBackend to debug login issues

1.0.2

• Fix missing next URL from initial login form data (#11)

1.0.1

• Improve documentation :)

1.0.0

• Add Python 3.8 support
• Add Django 3.0 support
• Add Wagtail support
• Drop Django 2.0 support
• Drop Django 2.1 support
• Move CI and Release suite to GitHub actions