The Wire · Showcase
DJANGO DOCUMENTATION STANDARDS CLEANUP UNDERWAY AS CVE METADATA HANDLING TIGHTENS
By RepoJournal · Filed · About Django
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
FAQ
- What changed 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.
- What should Django teams do about it?
- Review your Django docstring conventions against the new guidelines to avoid future rejections • If you maintain security advisories, audit your CVE descriptions for proper product naming and code formatting • Monitor the feature release cycle - version bumps suggest an announcement is coming
- Which Django repositories shipped on May 27, 2026?
- django/django, django/djangoproject.com