[pull] main from django:main

docs/internals/contributing/writing-code/submitting-patches.txt

@@ -438,9 +438,6 @@ All code changes
 * If the change is backwards incompatible in any way, is there a note
   in the release notes (``docs/releases/A.B.txt``)?
 * Is Django's test suite passing?
-* If there is a :ref:`code coverage report <code-coverage-on-pull-requests>`
-  comment on the pull request, have you reviewed the missing coverage in
-  context (considering database/platform-specific limitations)?
 * If the change affects the Django admin or rendered HTML output, has
   :ref:`accessibility testing <accessibility-testing-baseline>` been done?
 

docs/internals/contributing/writing-code/unit-tests.txt

@@ -394,49 +394,6 @@ settings file  defines ``coverage_html`` as the output directory for the report
 and also excludes several directories not relevant to the results
 (test code or external code included in Django).
 
-.. _code-coverage-on-pull-requests:
-
-Code coverage on pull requests
-------------------------------
-
-Django's continuous integration (CI) system automatically runs code coverage
-analysis on pull requests and posts a comment with a diff coverage report. This
-helps reviewers see which lines in the changed code are covered by tests.
-
-**What the coverage report shows:**
-
-The coverage report posted on pull requests uses `diff-cover`_ to analyze only
-the lines that were changed or added in the PR. It shows:
-
-* Lines that are covered by tests (✓)
-* Lines that are not covered by tests (✗)
-* Lines that cannot be covered (e.g., comments, blank lines)
-
-.. _diff-cover: https://github.com/Bachmann1234/diff_cover
-
-**Important limitations:**
-
-When reviewing coverage reports on pull requests, keep these limitations in
-mind:
-
-* **Database-specific code:** The CI coverage job runs tests using SQLite on
-  Windows. Code paths specific to other databases (PostgreSQL, MySQL, Oracle)
-  will appear as "not covered" even if database-specific tests exist. This is
-  expected and acceptable.
-
-* **Platform-specific code:** Similarly, code that only runs on certain
-  operating systems (Linux, macOS) will appear as not covered when run on
-  Windows.
-
-* **Coverage doesn't equal quality:** A line being "covered" only means it was
-  executed during tests. It doesn't guarantee the line is well-tested or that
-  all edge cases are handled. During review, assess test quality beyond just
-  coverage numbers.
-
-
-Missing coverage should be considered a warning rather than a blocker and
-should be evaluated in context.
-
 .. _contrib-apps:
 
 Contrib apps

docs/releases/4.2.27.txt

@@ -0,0 +1,13 @@
+===========================
+Django 4.2.27 release notes
+===========================
+
+*December 2, 2025*
+
+Django 4.2.27 fixes one security issue with severity "high", one security issue
+with severity "moderate", and one bug in 4.2.26.
+
+Bugfixes
+========
+
+* ...

docs/releases/5.1.15.txt

@@ -0,0 +1,13 @@
+===========================
+Django 5.1.15 release notes
+===========================
+
+*December 2, 2025*
+
+Django 5.1.15 fixes one security issue with severity "high", one security issue
+with severity "moderate", and one bug in 5.1.14.
+
+Bugfixes
+========
+
+* ...

docs/releases/5.2.9.txt

@@ -2,9 +2,10 @@
 Django 5.2.9 release notes
 ==========================
 
-*Expected December 2, 2025*
+*December 2, 2025*
 
-Django 5.2.9 fixes several bugs in 5.2.8.
+Django 5.2.9 fixes one security issue with severity "high", one security issue
+with severity "moderate", and several bugs in 5.2.8.
 
 Bugfixes
 ========

docs/releases/index.txt

@@ -55,6 +55,7 @@ versions of the documentation contain the release notes for any later releases.
 .. toctree::
    :maxdepth: 1
 
+   5.1.15
    5.1.14
    5.1.13
    5.1.12
@@ -98,6 +99,7 @@ versions of the documentation contain the release notes for any later releases.
 .. toctree::
    :maxdepth: 1
 
+   4.2.27
    4.2.26
    4.2.25
    4.2.24

zizmor.yml

@@ -1,7 +1,6 @@
 rules:
   dangerous-triggers:
     ignore:
-      - coverage.yml
       - labels.yml
       - new_contributor_pr.yml
   unpinned-uses: