Update Python modules (Django 4.2.16, etc.)

[TimidRobot]

Fixes

• 🔴 Django SQL injection vulnerability · CVE-2024-42005 · GitHub Advisory Database
• 🟠 Django vulnerable to Denial of Service · CVE-2024-39614 · GitHub Advisory Database
  
• 🟠 Django Path Traversal vulnerability · CVE-2024-39330 · GitHub Advisory Database
• 🟠 Django vulnerable to Denial of Service · CVE-2024-38875 · GitHub Advisory Database
• 🟡 Django vulnerable to denial-of-service attack · CVE-2024-41991 · GitHub Advisory Database
• 🟡 Django vulnerable to a denial-of-service attack · CVE-2024-41990 · GitHub Advisory Database
• 🟡 Django memory consumption vulnerability · Dependabot alert #44 · creativecommons/cc-legal-tools-app
• 🟡 Django vulnerable to user enumeration attack · CVE-2024-39329 · GitHub Advisory Database

Description

• Update Python modules
• ⚠️ Requires docker images to be rebuilt (docker compose build)

Technical details

--- piplist.old	2024-09-12 06:47:03
+++ piplist.new	2024-09-12 06:47:03
@@ -4 +4 @@
-Babel                2.15.0
+babel                2.16.0
@@ -6,2 +6,2 @@
-black                24.4.2
-certifi              2024.6.2
+black                24.8.0
+certifi              2024.8.30
@@ -12 +12 @@
-coverage             7.5.4
+coverage             7.6.1
@@ -15,6 +15,6 @@
-Django               4.2.13
-django-debug-toolbar 4.4.2
-factory-boy          3.3.0
-Faker                25.9.1
-filelock             3.15.4
-flake8               7.1.0
+Django               4.2.16
+django-debug-toolbar 4.4.6
+factory_boy          3.3.1
+Faker                28.4.1
+filelock             3.16.0
+flake8               7.1.1
@@ -24,2 +24,2 @@
-identify             2.5.36
-idna                 3.7
+identify             2.6.0
+idna                 3.8
@@ -28 +28 @@
-lxml                 5.2.2
+lxml                 5.3.0
@@ -35 +35 @@
-pip                  24.0
+pip                  24.2
@@ -37 +37 @@
-platformdirs         4.2.2
+platformdirs         4.3.2
@@ -39,2 +39,2 @@
-pre-commit           3.7.1
-pycodestyle          2.12.0
+pre-commit           3.8.0
+pycodestyle          2.12.1
@@ -42 +42 @@
-pyparsing            3.1.2
+pyparsing            3.1.4
@@ -45 +45 @@
-PyYAML               6.0.1
+PyYAML               6.0.2
@@ -47 +47 @@
-regex                2024.5.15
+regex                2024.9.11
@@ -49 +49 @@
-setuptools           70.1.0
+setuptools           74.1.2
@@ -52,2 +52,2 @@
-soupsieve            2.5
-sqlparse             0.5.0
+soupsieve            2.6
+sqlparse             0.5.1
@@ -57,3 +57,3 @@
-urllib3              2.2.2
-virtualenv           20.26.3
-wheel                0.43.0
+urllib3              2.2.3
+virtualenv           20.26.4
+wheel                0.44.0

Tests

Unit tests and coverage

command:

./dev/coverage.sh

output excerpt:

Name    Stmts   Miss Branch BrPart    Cover   Missing
-----------------------------------------------------
TOTAL    1741      0    668      0  100.00%

20 files skipped due to complete coverage.

Published files

• verified that the Python module updates do not cause any changes to published files
  1. cc-legal-tools-app: Published files:
     • command:

       docker compose exec app ./manage.py publish -v2

  2. cc-legal-tools-data: verified there were no changes:
     • command:

       git status

     • output excerpt:

       nothing to commit, working tree clean
       

Checklist

• My pull request has a descriptive title (not a vague title like Update index.md).
• My pull request targets the default branch of the repository (main or master).
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added or updated tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no
  visible errors.

Developer Certificate of Origin

For the purposes of this DCO, "license" is equivalent to "license or public domain dedication," and "open source license" is equivalent to "open content license or public domain dedication."

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.