Release notes Django 1.6.3 release notes

The CSRF-protection system is based on a random nonce sent to the client in a cookie which must be sent by the client on future requests and, in forms, a hidden value which must be submitted back with the form.

Release notes Django 1.7 release notes Features deprecated in 1.7

If you relied on these methods to alter structures like form fields, you should now treat these OrderedDicts as immutable objects and override them to change their content.

Release notes Django 1.8 release notes Backwards incompatible changes in 1.8

InlineModelAdmin now has an attribute show_change_link that supports showing a link to an inline object’s change form. Use the new django.contrib.admin.RelatedOnlyFieldListFilter in ModelAdmin.list_filter to limit the list_filter choices to foreign objects which are attached to those from the ModelAdmin.

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

The new SingleObjectMixin.query_pk_and_slug attribute allows changing the behavior of get_object() so that it’ll perform its lookup using both the primary key and the slug. The get_form() method doesn’t require a form_class to be provided anymore.

Release notes Django 1.8 release notes Features deprecated in 1.8

The original_content_type_id attribute on InlineAdminForm has been deprecated and will be removed in Django 1.10. Historically, it was used to construct the “view on site” URL. This URL is now accessible using the absolute_url attribute of the form.

Release notes Django 1.8.8 release notes

Corrected __len query lookup on ArrayField for empty arrays (#25772). Restored the ability to use custom formats from formats.py with django.utils.formats.get_format() and the date template filter (#25812). Fixed a state bug when migrating a SeparateDatabaseAndState operation backwards (#25896).

Release notes

This release starts Django’s use of a loose form of semantic versioning, but there aren’t any major backwards incompatible changes that might be expected of a 2.0 release. Upgrading should be a similar amount of effort as past feature releases.

Release notes Django 2.0 release notes Backwards incompatible changes in 2.0

If you want to preserve the 30 character limit for last names, use a custom form: If you wish to keep this restriction in the admin when editing users, set UserAdmin.form to use this form:

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

The new ModelAdmin.get_deleted_objects() method allows customizing the deletion process of the delete view and the “delete selected” action. The actions.html, change_list_results.html, date_hierarchy.html, pagination.html, prepopulated_fields_js.html, search_form.html, and submit_line.html templates can now be overridden per app or per model (besides overridden globally).

Release notes Django 2.1 release notes Features deprecated in 2.1

Support for SQLite < 3.7.15 is removed. The date format of Set-Cookie’s Expires directive is changed to follow RFC 7231 Section 7.1.1.1 instead of Netscape’s cookie standard. Hyphens present in dates like Tue, 25-Dec-2018 22:26:13 GMT are removed.

Release notes Django 2.1.1 release notes

Fixed translation failure of DurationField’s “overflow” error message (#29623). Fixed a regression where the admin change form crashed if the user doesn’t have the ‘add’ permission to a model that uses TabularInline (#29637).

Release notes Django 2.1.15 release notes

… parent model but edit permissions to the inline model, would display a read-only view of the parent model but editable forms for the inline. Submitting these forms would not allow direct edits to the parent model, but would trigger the …

Release notes Django 2.1.2 release notes

Fixed a crash when a user with the view (but not change) permission made a POST request to an admin user change form (#29809).

Release notes Django 2.2.8 release notes

… parent model but edit permissions to the inline model, would display a read-only view of the parent model but editable forms for the inline. Submitting these forms would not allow direct edits to the parent model, but would trigger the …

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

Django now includes models.JSONField and forms.JSONField that can be used on all supported database backends. Both fields support the use of custom JSON encoders and decoders.

Release notes Django 3.1 release notes Backwards incompatible changes in 3.1

If you want to preserve the 30 character limit for first names, use a custom form: If you wish to keep this restriction in the admin when editing users, set UserAdmin.form to use this form:

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

The new absolute_max argument for formset_factory(), inlineformset_factory(), and modelformset_factory() allows customizing the maximum number of forms that can be instantiated when supplying POST data. See Limiting the maximum number of instantiated forms for more details.

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

The admin history view is now paginated. Related widget wrappers now have a link to object’s change form. The AdminSite.get_app_list() method now allows changing the order of apps and models on the admin index page.

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

A nested atomic block marked as durable in django.test.TestCase now raises a RuntimeError, the same as outside of tests. SimpleTestCase.assertFormError() and assertFormsetError() now support passing a form/formset object directly.

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

The new AdminUserCreationForm and the existing AdminPasswordChangeForm now support disabling password-based authentication by setting an unusable password on form save. This is now available in the admin when visiting the user creation and password change pages.