summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorNatalia <124304+nessita@users.noreply.github.com>2025-04-30 11:23:51 -0300
committernessita <124304+nessita@users.noreply.github.com>2025-04-30 14:55:12 -0300
commit0f5dd0dff3049189a3fe71a62670b746543335d5 (patch)
treeb013d59ec8100f22bf3c19fa0772f5d3bb249de3 /docs
parent66f9eb0ff1e7147406318c5ba609729678e4e6f6 (diff)
Made cosmetic edits and added upcoming security release to release notes.
Diffstat (limited to 'docs')
-rw-r--r--docs/releases/4.2.21.txt3
-rw-r--r--docs/releases/5.1.9.txt3
-rw-r--r--docs/releases/5.2.1.txt7
3 files changed, 8 insertions, 5 deletions
diff --git a/docs/releases/4.2.21.txt b/docs/releases/4.2.21.txt
index 1064dcf202..306269a3e7 100644
--- a/docs/releases/4.2.21.txt
+++ b/docs/releases/4.2.21.txt
@@ -4,7 +4,8 @@ Django 4.2.21 release notes
*Expected May 7, 2025*
-Django 4.2.21 fixes a data loss bug and a regression in 4.2.20.
+Django 4.2.21 fixes a security issue with severity "moderate", a data loss bug,
+and a regression in 4.2.20.
Bugfixes
========
diff --git a/docs/releases/5.1.9.txt b/docs/releases/5.1.9.txt
index 50daaf7528..dec03a6964 100644
--- a/docs/releases/5.1.9.txt
+++ b/docs/releases/5.1.9.txt
@@ -4,7 +4,8 @@ Django 5.1.9 release notes
*Expected May 7, 2025*
-Django 5.1.9 fixes a data loss bug and a regression in 5.1.8.
+Django 5.1.9 fixes a security issue with severity "moderate", a data loss bug,
+and a regression in 5.1.8.
Bugfixes
========
diff --git a/docs/releases/5.2.1.txt b/docs/releases/5.2.1.txt
index 67244c590f..1f696a7551 100644
--- a/docs/releases/5.2.1.txt
+++ b/docs/releases/5.2.1.txt
@@ -4,7 +4,8 @@ Django 5.2.1 release notes
*Expected May 7, 2025*
-Django 5.2.1 fixes several bugs in 5.2.
+Django 5.2.1 fixes a security issue with severity "moderate" and several bugs
+in 5.2.
Bugfixes
========
@@ -56,8 +57,8 @@ Bugfixes
on a ``QuerySet`` filtered against a related model and including references
to annotations through ``values()`` (:ticket:`36360`).
-* Fixed a bug in composite primary key introspection that caused
- ``IntegerField`` to be wrongly identified as ``AutoField`` on SQLite
+* Fixed a bug in Django 5.2 that caused composite primary key introspection to
+ wrongly identify ``IntegerField`` as ``AutoField`` on SQLite
(:ticket:`36358`).
* Fixed a bug in Django 5.2 that caused a redundant ``unique_together``