Release notes Django 4.0 release notes Backwards incompatible changes in 4.0

DeleteView now uses FormMixin to handle POST requests. As a consequence, any custom deletion logic in delete() handlers should be moved to form_valid(), or a shared helper method, if required.

Release notes Django 4.1 release notes What’s new in Django 4.1Minor features

The default template used to render forms when cast to a string, e.g. in templates as {{ form }}, is now configurable at the project-level by setting form_template_name on the class provided for FORM_RENDERER.

Release notes Django 4.1 release notes What’s new in Django 4.1Minor features

For example, for the <p> output style used by as_p(), you would define a form renderer setting form_template_name to "django/forms/p.html" and formset_template_name to "django/forms/formsets/p.html".

Release notes Django 4.1 release notes Features deprecated in 4.1

Use POST requests instead. If you want to retain the user experience of an HTML link, you can use a form that is styled to appear as a link:

Release notes Django 4.2 release notes What’s new in Django 4.2Minor features

UserCreationForm now saves many-to-many form fields for a custom user model. The new BaseUserCreationForm is now the recommended base class for customizing the user creation form.

Release notes Django 5.0 release notes What’s new in Django 5.0

Field.choices (for model fields) and ChoiceField.choices (for form fields) allow for more flexibility when declaring their values.

Release notes Django 5.0 release notes What’s new in Django 5.0Minor features

In order to improve accessibility, the following changes are made: Form fields now include the aria-describedby HTML attribute to enable screen readers to associate form fields with their help text. Invalid form fields now include the aria-invalid="true" HTML attribute.

Release notes Django 5.1 release notes What’s new in Django 5.1Minor features

In order to improve accessibility and enable screen readers to associate fieldsets with their help text, the form fieldset now includes the aria-describedby HTML attribute.

Release notes Django 6.0 release notes What’s new in Django 6.0Minor features

The new AdminSite.password_change_form attribute allows customizing the form used in the admin site password change view. Message levels messages.DEBUG and messages.INFO now have distinct icons and CSS styling. Previously, both levels shared the same appearance as messages.SUCCESS.

Release notes Django 6.0.2 release notes

Fixed a visual regression in Django 6.0 for admin form fields grouped under a <fieldset> aligned horizontally (#36788).

Release notes Archive of security issues Issues under Django’s security process

Potential log injection via unescaped geometry form values. Full description Django 6.1 (patch) Django 6.0 (patch) Django 5.2 (patch)

Release notes Archive of security issues Issues under Django’s security process

Potential account hijack via password reset form. Full description

Release notes Django 5.2.18 release notes

Model formsets incorrectly allowed forged POST data to either delete instances outside the limiting queryset or create instances via edit-only formsets when the model’s primary key could be set through the form, such as with: a OneToOneField (or parent link …

Release notes Django 6.0.9 release notes

Model formsets incorrectly allowed forged POST data to either delete instances outside the limiting queryset or create instances via edit-only formsets when the model’s primary key could be set through the form, such as with: a OneToOneField (or parent link …

Release notes Django version 0.96 release notes Backwards-incompatible changes

The format of the constraint names Django generates for foreign key references have changed slightly.

Release notes Porting your apps from Django 0.96 to 1.0 Common changes

The Django administrative interface (django.contrib.admin) has been completely refactored; admin definitions are now completely decoupled from model definitions, the framework has been rewritten to use Django’s new form-handling library and redesigned with extensibility and customization in mind.

Release notes Porting your apps from Django 0.96 to 1.0 Less-common changesInternationalization

This means you can no longer use a link to access the view, but must use a form submission of some kind (e.g. a button).

Release notes Django 1.1 release notes What’s new in Django 1.1

Instances of Django forms (see the forms overview) now have two additional methods, hidden_fields() and visible_fields(), which return the list of hidden – i.e., <input type="hidden"> – and visible fields on the form, respectively.

Release notes Django 1.1.2 release notes

Django 1.2 (the next major release of Django) will contain a feature that will improve protection against Cross-Site Request Forgery (CSRF) attacks. This feature requires the use of a new csrf_token template tag in all forms that Django renders.

Release notes Django 1.10 release notes What’s new in Django 1.10Minor features

The success message that appears after adding or editing an object now contains a link to the object’s change form. All inline JavaScript is removed so you can enable the Content-Security-Policy HTTP header if you wish.