Releases: apragacz/django-rest-registration
Releases · apragacz/django-rest-registration
0.5.1
Changes:
- Allow TokenAuthentication subclasses (pull request #74)
- Fix for issue #52: Check whether valid Django authentication backend is being used
- Change email verification signal added (pull request #69)
- More restrictive linters: pylint with improved config, flake8-comprehensions plugin added
- Force to use Django REST Framework version lower than 3.10 (this limitation will be removed in 0.6.0)
0.5.0
Changes:
- Fix critical security issue with misusing the Django Signer API. Thanks for @peterthomassen for finding the bug! you can read more about it here.
- Issue #57: Pass request in serializer context in all views
- Added signals for injecting logic in user registration
0.4.5
Changes:
- Resolved issue #48: Allowing to use custom user field for verification
- Resolved issue #46: added
SEND_RESET_PASSWORD_LINK_SERIALIZER_USE_EMAIL setting
- Resolved issue #50: customizable send reset password link serializer
- Fixed reset password in case user is unverified and one-time use is enabled
0.4.4
Changes:
- Resolved issue #44
- Resolved issue #45
0.4.3
Changes:
- Updated documentation and README
0.4.2
Changes:
- Resolved issue #39
- Resolved issue #40
0.4.1
Changes:
- Resolved #36
- improvements in the documentation
0.4.0
Upgrading to major version
0.3.14
Changes:
- Fix: Added permission classes in case of endpoints using anonymous users.
- Added
RESET_PASSWORD_VERIFICATION_ENABLED
- More liberal checks for
VERIFICATION_FROM_EMAIL
- Implementation details concerning settings fields and
NestedSettings
0.3.13
Changes:
- Resolved issue #29: Added
RESET_PASSWORD_VERIFICATION_ONE_TIME_USE
setting
- Dropped support of Django 1.10, added explicit support of Django 2.1