diff --git a/.github/workflows/labels.yml b/.github/workflows/labels.yml
index 2f319627c72c..3042f4d22810 100644
--- a/.github/workflows/labels.yml
+++ b/.github/workflows/labels.yml
@@ -21,10 +21,6 @@ jobs:
     runs-on: ubuntu-latest
     timeout-minutes: 60
     steps:
-      - uses: actions/checkout@v6
-        with:
-          persist-credentials: false
-
       - name: "Check title and manage labels"
         uses: actions/github-script@v8
         with:
diff --git a/docs/intro/tutorial07.txt b/docs/intro/tutorial07.txt
index ab77f2b5400e..3e963d32804e 100644
--- a/docs/intro/tutorial07.txt
+++ b/docs/intro/tutorial07.txt
@@ -109,12 +109,12 @@ the database. Django knows that a :class:`~django.db.models.ForeignKey` should
 be represented in the admin as a ``<select>`` box. In our case, only one
 question exists at this point.
 
-Also note the "Add another question" link next to "Question." Every object with
-a ``ForeignKey`` relationship to another gets this for free. When you click
-"Add another question", you'll get a popup window with the "Add question" form.
-If you add a question in that window and click "Save", Django will save the
-question to the database and dynamically add it as the selected choice on the
-"Add choice" form you're looking at.
+Also note the "Add another question" button (displayed as a plus sign) to the
+right of the "Question" field. Every ``ForeignKey`` relationship gets this
+button for free. When you click this button, you'll get a popup window with the
+"Add question" form. If you add a question in that window and click "Save",
+Django will save the question to the database and dynamically add it as the
+selected choice on the "Add choice" form you're looking at.
 
 But, really, this is an inefficient way of adding ``Choice`` objects to the
 system. It'd be better if you could add a bunch of Choices directly when you
diff --git a/docs/ref/forms/widgets.txt b/docs/ref/forms/widgets.txt
index 80047aabc5e9..c65063cd68a4 100644
--- a/docs/ref/forms/widgets.txt
+++ b/docs/ref/forms/widgets.txt
@@ -646,6 +646,29 @@ These widgets make use of the HTML elements ``input`` and ``textarea``.
     :doc:`/topics/i18n/formatting`. ``%U``, ``%W``, and ``%j`` formats are not
     supported by this widget.
 
+    .. admonition:: Using the HTML5 "date" input type
+
+        If you are targeting browsers that support the
+        `HTML5 "date" input type`_, you can override the ``input_type``
+        attribute to enable the browser’s native date picker::
+
+            class MyDateInput(forms.DateInput):
+                input_type = "date"
+                format = "%Y-%m-%d"
+
+        Alternatively::
+
+            DateInput(attrs={"type": "date"}, format="%Y-%m-%d")
+
+        HTML5 date inputs expect values in the ISO format ``YYYY-MM-DD``. If a
+        different format is provided, the field may appear empty even when a
+        value exists. Setting the ``format`` attribute controls how Django
+        provides the value, but the browser controls how it is displayed.
+        Hence, the ``format`` attribute and the :setting:`DATE_INPUT_FORMATS`
+        setting will have no effect on the displayed value.
+
+        .. _HTML5 "date" input type: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/date
+
 ``DateTimeInput``
 ~~~~~~~~~~~~~~~~~
 
diff --git a/zizmor.yml b/zizmor.yml
index 23630337b48c..19493ba151db 100644
--- a/zizmor.yml
+++ b/zizmor.yml
@@ -1,5 +1,7 @@
 rules:
   dangerous-triggers:
+    # Before ignoring a file, assume all inputs are malicious, assign explicit
+    # minimal permissions, and do not use actions/checkout.
     ignore:
       - coverage_comment.yml
       - labels.yml