Log message:
py-django: updated to 5.1.6

Django 5.1.6 fixes several bugs in 5.1.5.

Bugfixes

Fixed a regression in Django 5.1.5 that caused validate_ipv6_address() and \ 
validate_ipv46_address() to crash when handling non-string values

Fixed a regression in Django 5.1 where password fields, despite being set to \ 
required=False, were still treated as required in forms derived from \ 
BaseUserCreationForm

Log message:
py-django: updated to 5.1.5

Django 5.1.5 fixes a security issue with severity “moderate” and one bug in \ 
5.1.4.

CVE-2024-56374: Potential denial-of-service vulnerability in IPv6 validation

Lack of upper bound limit enforcement in strings passed when performing IPv6 \ 
validation could lead to a potential denial-of-service attack. The undocumented \ 
and private functions clean_ipv6_address and is_valid_ipv6_address were \ 
vulnerable, as was the django.forms.GenericIPAddressField form field, which has \ 
now been updated to define a max_length of 39 characters.

The django.db.models.GenericIPAddressField model field was not affected.

Bugfixes

Fixed a crash when applying migrations with references to the removed \ 
Meta.index_together option

Log message:
py-django: updated to 5.1.4

5.1.4

Django 5.1.4 fixes one security issue with severity “high”, one security \ 
issue with severity “moderate”, and several bugs in 5.1.3.

CVE-2024-53907: Denial-of-service possibility in strip_tags()

strip_tags() would be extremely slow to evaluate certain inputs containing large \ 
sequences of nested incomplete HTML entities. The strip_tags() method is used to \ 
implement the corresponding striptags template filter, which was thus also \ 
vulnerable.

strip_tags() now has an upper limit of recursive calls to HTMLParser before \ 
raising a SuspiciousOperation exception.

Remember that absolutely NO guarantee is provided about the results of \ 
strip_tags() being HTML safe. So NEVER mark safe the result of a strip_tags() \ 
call without escaping it first, for example with django.utils.html.escape().

CVE-2024-53908: Potential SQL injection via HasKey(lhs, rhs) on Oracle

Direct usage of the django.db.models.fields.json.HasKey lookup on Oracle was \ 
subject to SQL injection if untrusted data was used as a lhs value.

Applications that use the has_key lookup through the __ syntax are unaffected.

Bugfixes

Fixed a crash in createsuperuser on Python 3.13+ caused by an unhandled OSError \ 
when the username could not be determined

Fixed a regression in Django 5.1 where relational fields were not updated when \ 
calling Model.refresh_from_db() on instances with deferred fields

Log message:
py-*: remove unused tool dependency

py-setuptools includes the py-wheel functionality nowadays

Log message:
py-django: updated to 5.1.3

Django 5.1.3 fixes several bugs in 5.1.2 and adds compatibility with Python 3.13.

Bugfixes

Fixed a bug in Django 5.1 where DomainNameValidator accepted any input value \ 
that contained a valid domain name, rather than only input values that were a \ 
valid domain name

Fixed a regression in Django 5.1 that prevented the use of DB-IP databases with \ 
GeoIP2

Fixed a regression in Django 5.1 where non-ASCII fieldset names were not \ 
displayed when rendering admin fieldsets

Log message:
*: clean-up after python38 removal

Log message:
py-django: updated to 5.1.2

5.1.2

Fixed a regression in Django 5.1 that caused a crash when using the PostgreSQL \ 
lookup trigram_similar on output fields from Concat
Fixed a regression in Django 5.1 that caused a crash of JSONObject() when using \ 
server-side binding with PostgreSQL 16+
Fixed a regression in Django 5.1 that made selected items in multi-select \ 
widgets indistinguishable from non-selected items in the admin dark theme

Log message:
py-django: updated to 5.0.6

Django 5.0.6 fixes a packaging error in 5.0.5.