The Django team is happy to announce the release of Django 4.0.
In accordance with our security release policy, the Django team is issuing Django 3.2.4, Django 3.1.12, and Django 2.2.24. These release addresses the security issue detailed below. We encourage all users of Django to upgrade as soon as possible.
Today we've issued 3.2.3, 3.1.11, and 2.2.23 bugfix releases. The release package and checksums are available from our downloads page, as well as from the Python Package Index. The PGP key ID used for this release is Mariusz Felisiak: 2EF56372BA48CD1B.
In accordance with our security release policy, the Django team is issuing Django 3.2.2, Django 3.1.10, and Django 2.2.22. These releases address the security issue with severity "moderate" detailed below. We encourage all users of Django to upgrade as soon as possible.
In accordance with our security release policy, the Django team is issuing Django 3.2.1, Django 3.1.9, and Django 2.2.21. These release addresses the security issue detailed below. We encourage all users of Django to upgrade as soon as possible.
In accordance with the security release policies that Django and Jazzband are following, the Jazzband project team for the Django Debug Toolbar project is issuing Django Debug Toolbar 3.2.1, Django Debug Toolbar 2.2.1 and Django Debug Toolbar 1.11.1. These releases address the security issue with severity "high" detailed below. We encourage all users of Django Debug Toolbar to upgrade as soon as possible.
The Django team is happy to announce the release of Django 3.2. This version has been designated as a long-term support (LTS) release, which means that security and data loss fixes will be applied for at least the next three years. It will also receive fixes for crashing bugs, major functionality bugs in newly-introduced features, and regressions from older versions of Django for the next eight months until December 2021.
In accordance with our security release policy, the Django team is issuing Django 3.1.8, Django 3.0.14 and Django 2.2.20. These releases address the security issue with severity "low" detailed below. We encourage all users of Django to upgrade as soon as possible.
Django 3.2 release candidate 1 is the final opportunity for you to try out the mezcla of new features before Django 3.2 is released.
Django 3.2 beta 1 is now available. It represents the second stage in the 3.2 release cycle and is an opportunity for you to try out the changes coming in Django 3.2.
In accordance with our security release policy, the Django team is issuing Django 3.1.7, Django 3.0.13, and Django 2.2.19. These release addresses the security issue detailed below. We encourage all users of Django to upgrade as soon as possible.
In accordance with our security release policy, the Django team is issuing Django 3.1.6, Django 3.0.12 and Django 2.2.18. These releases address the security issue with severity "low" detailed below. We encourage all users of Django to upgrade as soon as possible.
Django 3.2 alpha 1 is now available. It represents the first stage in the 3.2 release cycle and is an opportunity for you to try out the changes coming in Django 3.2.
Today we've issued the 3.1.5 bugfix release. The release package and checksums are available from our downloads page, as well as from the Py
In accordance with our security release policy, the Django team is issuing Channels 3.0.3. This release addresses the security issue detailed below. We encourage all users of Channels to upgrade as soon as possible.
Today we've issued the 3.1.4 bugfix release. The release package and checksums are available from our downloads page, as well as from the Python Package Index. The PGP key ID used for this release is Mariusz Felisiak: 2EF56372BA48CD1B.
Today we've issued 3.1.3, 3.0.11, and 2.2.17 bugfix releases. The release package and checksums are available from our downloads page, as well as from the Python Package Index. The PGP key ID used for this release is Carlton Gibson: E17DF5C82B4F9D00.
Django 3.0 beta 1 is now available. It represents the second stage in the 3.0 release cycle and is an opportunity for you to try out the changes coming in Django 3.0.
Today we've issued the 2.2.6, 2.1.13, and 1.11.25 bugfix releases. The release package and checksums are available from our downloads page, as well as from the Python Package Index. The PGP key ID used for this release is Carlton Gibson: E17DF5C82B4F9D00.
Django 3.0 alpha 1 is now available. It represents the first stage in the 3.0 release cycle and is an opportunity for you to try out the changes coming in Django 3.0.