126 wires and counting

$ follow Django

Keep up with Django in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-07-25
stories 15

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

DJANGO ADMIN PERMISSION CHECKS NOW CONSISTENT ACROSS ALL VIEWS

By RepoJournal · Filed · About Django · Composed from the cited sources · methodology

Django fixed a permission inconsistency in admin views that could have exposed data to staff users lacking proper access.

The admin interface now enforces uniform permission checks across all views [1]. Previously, view_on_site and history views could be accessed by staff without the required view or change permissions, while changeform and autocomplete views properly blocked access. This fix ensures that an HTTP 403 response is returned consistently when a user lacks the necessary permissions [2]. Beyond security, Django's docs got a housekeeping pass: outdated Python 2 references were stripped from contributing guidelines [3], email documentation typos were corrected with proper versionadded annotations [4], and a grab bag of accumulated typos across the codebase is staged for merge [5]. Over on djangoproject.com, the team bumped four Docker GitHub Actions in quick succession: docker/metadata-action, docker/login-action, docker/build-push-action, and docker/setup-compose-action, all preserving esbuild bundle names for consistency [6] [7] [8] [9].

Action items

References

  1. [1] Fixed #37160 -- Made admin views raise PermissionDenied consistently. ↗ django/django
  2. [2] Fixed #37160 -- Made admin views raise PermissionDenied consistently. ↗ django/django
  3. [3] Removed outdated Python 2 references from contributing docs. ↗ django/django
  4. [4] Fixed typo and versionadded locations in email docs. ↗ django/django
  5. [5] Grab bag of typo fixes. ↗ django/django
  6. [6] Bump docker/metadata-action from 6.1.0 to 6.2.0 ↗ django/djangoproject.com
  7. [7] Bump docker/login-action from 4.2.0 to 4.4.0 ↗ django/djangoproject.com
  8. [8] Bump docker/build-push-action from 7.2.0 to 7.3.0 ↗ django/djangoproject.com
  9. [9] Bump docker/setup-compose-action from 2.2.0 to 2.3.0 ↗ django/djangoproject.com

Quick answers

What shipped in Django on July 25, 2026?
Django fixed a permission inconsistency in admin views that could have exposed data to staff users lacking proper access. In total, 8 commits and 7 pull requests landed.
Who contributed to Django on July 25, 2026?
4 developers shipped this update, including nessita, jacobtylerwalls, Mike Edmunds, and dependabot.
What were the notable Django updates?
Fixed #37160 -- Made admin views raise PermissionDenied consistently, Fixed #37160 -- Made admin views raise PermissionDenied consistently, and Removed outdated Python 2 references from contributing docs.