Add a Change History to PEP 1

Author: warsaw

peps/pep-0001.rst

@@ -585,9 +585,9 @@ Each PEP should have the following parts/sections:
     Think of this as a "changelog" or "release notes" for the PEP.  In general, whenever you update the
     ``Post-History`` header for major changes, add a new bullet item in newest-first (i.e. reverse
     chronological) order, using the same ``MMM-DD-YYYY`` format, with sub-bullets summarizing the changes.
-    This isn't mandatory, so it's left to the PEP author's discretion, but such a section can be helpful for
-    those following along to understand the evolution of your PEP.  Here is :pep:`an example
-    <694#change-history>`.
+    You can consider linking this to the same link as the ``Post-History`` link.  This isn't mandatory, so
+    it's left to the PEP author's discretion, but such a section can be helpful for those following along to
+    understand the evolution of your PEP.  Here is :pep:`an example <694#change-history>`.
 
 15. Copyright/license -- Each new PEP must be placed under a dual license of
     public domain and CC0-1.0-Universal_ (see this PEP for an example).
@@ -884,6 +884,14 @@ Footnotes
 .. _Contributing Guide: https://github.com/python/peps/blob/main/CONTRIBUTING.rst
 
 
+Change History
+==============
+
+* 2026-02-02
+
+  * Added an optional ``Change History`` section for PEPs, for summarizing changes when updating the
+    ``Post-History`` header.
+
 Copyright
 =========
 

peps/pep-0012/pep-NNNN.rst

@@ -93,7 +93,8 @@ Change History
 
 [A summary of major changes the PEP has undergone.  Whenever you update the ``Post-History``, add a new bullet
 item in newest-first (i.e. reverse chronological) order, using the same ``MMM-DD-YYYY`` format, with
-sub-bullets summarizing the changes.]
+sub-bullets summarizing the changes.  You can use the same link for the date bullet as you do in the
+``Post-History`` addition.]
 
 
 Copyright