Django: Authentication Updates and Documentation Improvements

Transcript

Good morning. This is your Django developer briefing for May 28th, 2026.

Yesterday saw significant activity with six merged pull requests addressing authentication, documentation, and framework modernization.

Vishwa merged a fix for issue 37019, updating Django's login and logout functions to properly set request.auser when present on the request object. This resolves async authentication handling that was previously inconsistent.

Tim Harris merged the deprecation of JsonResponse's safe parameter, addressing issue 36905. The change removes a legacy security check that's been unnecessary since ECMAScript 5, bringing Django in line with other modern frameworks.

Jacob Walls merged updates to security release note links, improving navigation to severity level documentation across 14 release note files spanning versions 2.2 through 5.2.

Carlton Gibson merged documentation improvements for async views, specifically covering method_decorator usage on dispatch methods for View subclasses with async handlers.

Nessita enhanced the Django release script with better testing capabilities and commit hash tracking in checksum files. The improvements include new helper functions and comprehensive test coverage.

CodeQuiver updated database optimization documentation to remove outdated warnings about unlimited QuerySet.get results, reflecting changes made in earlier Django versions.

Additional commits included release note preparations for versions 6.0.6 and 5.2.15, and script refactoring to support isolated testing environments.

What's next: Watch for the upcoming 6.0.6 and 5.2.15 releases with their finalized release notes. The JsonResponse safe parameter deprecation will require attention in applications still using this feature.

That's your Django update for today.