v0.6.0

Breaking change for IP detection ⚠️

IP detection has now been delegated to the user to implement, as the configuration varies massively depending on the deployment environment. Now, BasicAuthIPWhitelistMiddleware uses request.META["REMOTE_ADDR"] as the client's IP, which corresponds to the IP address connecting to Django.

In most deployments, the X-Forwarded-For header can be used to correctly determine the client's IP. We recommend django-xff to help parse this header correctly. Because django-xff overrides REMOTE_ADDR by default, it is natively supported by BasicAuthIPWhitelistMiddleware.

What's Changed

• Upgrade test suite and metadata for Django 5.0 compatibility by @thibaudcolas in #15
• Update CI Django and Python versions by @tm-kn in #16
• Defer IP detection to the user by @RealOrangeOne in #23
• Adopt package into Torchbox by @RealOrangeOne in #24

New Contributors

• @thibaudcolas made their first contribution in #15
• @RealOrangeOne made their first contribution in #23

Full Changelog: v0.5...v0.6.0

v0.5a

Release: 0.5a

v0.3.4

CHANGELOG