Update .abi-compliance-history for change to enum ProcSignalReason

As noted in the commit message for 586f4266fb4, increasing the value of
NUM_PROCSIGNALS in enum ProcSignalReason breaks the ABI compatibility,
but no affected third-party code is known. Therefore this commit updates
.abi-compliance-history accordingly.

Discussion: https://postgr.es/m/CAHGQGwH_AAbtsiYDJt65N7_4PJ0CgOJmBEaCq68e5_tcuG_vXw@mail.gmail.com
Backpatch-through: 17 only

diff --git a/.abi-compliance-history b/.abi-compliance-history
index ed7eb9ffdaeaf4b32534da6b98cde901f4e87fbb..590b989094f6107a0b47ffde05929e5872e07dd0 100644 (file)
--- a/.abi-compliance-history
+++ b/.abi-compliance-history
@@ -18,6 +18,15 @@
 # Be sure to replace "<ADD JUSTIFICATION HERE>" with details of your change and
 # why it is deemed acceptable.
 
+586f4266fb4945f6ea3564b9c1bab093eb74bee4
+#
+# Fix ABI break by moving PROCSIG_SLOTSYNC_MESSAGE in ProcSignalReason
+# 2026-04-09 15:30:59 +0900
+#
+# This commit added PROCSIG_SLOTSYNC_MESSAGE just before the final entry,
+# NUM_PROCSIGNALS, in enum ProcSignalReason. This increased the value of
+# NUM_PROCSIGNALS, but no affected third-party code is known.
+
 4dac22aa10d2882c2e6fb465d7c314cc2d8fb754
 #
 # Add file_extend_method=posix_fallocate,write_zeros.