Who contributed to Django on May 27, 2026?

2 developers shipped this update, including nessita and jacobtylerwalls.

What were the notable Django updates?

Refs #35514 -- Removed specific Django versions from outside deprecated blocks, Removed version numbers from example tox -l output, and Refs #35870 -- Moved deprecated notice at the bottom for USE_BLANK_CHOICE_DASH.

@django

Python's batteries-included web framework

github ↗

Pick a date

Topics: Python Full archive →

The Wire · Showcase

DJANGO DOCUMENTATION STANDARDS CLEANUP UNDERWAY AS CVE METADATA HANDLING TIGHTENS

By RepoJournal · Filed 06:00 UTC on May 27, 2026 · About Django

2 people shipped this

nessita @nessita 2 cited

jacobtylerwalls @jacobtylerwalls 1 cited

Django's core team is systematically removing version numbers from outside deprecation blocks while the website team fixes critical security CVE metadata rendering issues.

The documentation cleanup is a deliberate push to enforce contributing guidelines [1]. Version numbers no longer appear in example outputs [2] and deprecated notices have been repositioned for clarity [3], with a second pass already underway to catch remaining violations [4]. Over on djangoproject.com, the security infrastructure got tighter: CVE descriptions now properly include the word 'Django' before version ranges [5], inline code backticks convert to HTML tags instead of rendering raw, and the tuple helper text bug is fixed [6]. The website team also added patch verification requests to the security release checklist [7] and improved how CWE and CAPEC IDs are handled in CVE metadata [8]. Version bumps across pre-commit, npm, and GitHub Actions suggest a feature release cycle is underway [9]. This is all infrastructure work, not features, but it matters: tighter security docs mean clearer vulnerability disclosures, and stricter documentation standards prevent future confusion.

Action items

→ Review your Django docstring conventions against the new guidelines to avoid future rejections django/django [plan]
→ If you maintain security advisories, audit your CVE descriptions for proper product naming and code formatting django/djangoproject.com [plan]
→ Monitor the feature release cycle - version bumps suggest an announcement is coming django/django [monitor]

References

[1] Refs #35514 -- Removed specific Django versions from outside deprecated blocks. django/django
[2] Removed version numbers from example tox -l output. django/django
[3] Refs #35870 -- Moved deprecated notice at the bottom for USE_BLANK_CHOICE_DASH. django/django
[4] Refs #35870, Refs #35514 -- Fixed a couple of issues for deprecation notices in 6.1 docs. ↗ django/django
[5] [checklists] Fixed CVE description to include product name and render inline code in HTML. ↗ django/djangoproject.com
[6] [checklists] Fixed CVE description to include product name and render inline code in HTML. django/djangoproject.com
[7] [checklists] Include request for patch verification in security checklist. django/djangoproject.com
[8] [checklists] Handle lists of CWE and CAPEC ids when building CVE metadata. django/djangoproject.com
[9] Bumped versions in pre-commit, npm, and GitHub Actions configurations. ↗ django/django

Quick answers

What shipped in Django on May 27, 2026?: Django's core team is systematically removing version numbers from outside deprecation blocks while the website team fixes critical security CVE metadata rendering issues. In total, 11 commits and 3 pull requests landed.
Who contributed to Django on May 27, 2026?: 2 developers shipped this update, including nessita and jacobtylerwalls.
What were the notable Django updates?: Refs #35514 -- Removed specific Django versions from outside deprecated blocks, Removed version numbers from example tox -l output, and Refs #35870 -- Moved deprecated notice at the bottom for USE_BLANK_CHOICE_DASH.

DJANGO ADMIN PERMISSION CHECKS NOW CONSISTENT ACROSS ALL VIEWS

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

python 15 shipped 1-min read

@django 1 day ago

DJANGO TIGHTENS THREADING FOR ASYNC ERROR HANDLING, GOVERNANCE FRAMEWORK SIMPLIFIED

Django patches a critical threading issue in async error response rendering that could cause database pool exhaustion and deadlock.

python 16 shipped 2-min read

@django 2 days ago

DJANGO 6.1 SUPPORT DATES SET AS DOCUMENTATION CLEANUP CONTINUES

Django pins end-of-support windows for 6.1 while the core team documents shared features between ModelAdmin and InlineModelAdmin.

python 8 shipped 1-min read

@django 3 days ago

DJANGO KILLS SIGNUP BOT ATTACK WITH RECAPTCHA, DAPHNE GAINS WEBSOCKET CONTROL

The Django project site plugged its only unprotected registration form after automated signups tanked email reputation, while Daphne now lets you configure WebSocket message sizes in development.

python 13 shipped 1-min read

Elsewhere on the wire

AI Agents about 9 hours ago

CLAUDE OPUS 5 LANDS ACROSS THE STACK

The newest Anthropic model is now live in langchain, Cline, and llama-index, with native support for extended reasoning and 1M context windows.

ai-agents 28 shipped 1-min read

Local LLMs about 9 hours ago

OLLAMA LANDS LAGUNA SUPPORT AND CRUSHES MEMORY LEAKS WHILE SGLANG HITS V0.5.16 WITH CONFIDENCE-DRIVEN SPECULATIVE DECODING

Ollama shipped three critical performance and reliability fixes for Metal residency and concurrent access patterns, while SGL-Lang released 0.5.16 with a new speculative algorithm hitting 383.7 tok/s on DeepSeek-V4.