From 3fb0e8bb129ae21616b5a8b6b839d688365f33c1 Mon Sep 17 00:00:00 2001
From: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
Date: Thu, 9 Jul 2026 13:47:11 +0300
Subject: [PATCH] Reinstate #updating-news-and-what-s-new-in-python anchor

---
 core-team/committing.rst | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/core-team/committing.rst b/core-team/committing.rst
index 0a5380e0f..6283c0508 100644
--- a/core-team/committing.rst
+++ b/core-team/committing.rst
@@ -68,7 +68,9 @@ to enter the public source tree. Ask yourself the following questions:
    if they haven't. For further questions about the CLA
    process, write to contributors@python.org.
 
-* **Were** ``What's New in Python`` **and** ``Misc/NEWS.d/next`` **updated?**
+* .. _updating-news-and-what-s-new-in-python:
+
+  **Were** ``What's New in Python`` **and** ``Misc/NEWS.d/next`` **updated?**
    If the change is particularly interesting for end users (for example, new features,
    significant improvements, or backwards-incompatible changes), then an
    entry in the ``What's New in Python`` document (in ``Doc/whatsnew/``) should