Update .abi-compliance-history for change to TransitionCaptureState.

As noted in the commit message for b4307ae2e54, the change to the
TransitionCaptureState structure is nominally an ABI break, but it is
not expected to affect any third-party code. Therefore, add it to the
.abi-compliance-history file.

Discussion: https://postgr.es/m/19380-4e293be2b4007248%40postgresql.org
Backpatch-through: 15-18

diff --git a/.abi-compliance-history b/.abi-compliance-history
index 79e3dfc8f5e188b36cd96812ce363aae3964ff40..6924edc72097cfa3a74df5d7d59db1aad8f7ceee 100644 (file)
--- a/.abi-compliance-history
+++ b/.abi-compliance-history
@@ -18,6 +18,17 @@
 # Be sure to replace "<ADD JUSTIFICATION HERE>" with details of your change and
 # why it is deemed acceptable.
 
+e7391bbf14db94afee1fd3c011314f7b8ee493e9
+#
+# Fix trigger transition table capture for MERGE in CTE queries.
+# 2026-01-24 11:30:50 +0000
+#
+# This commit changed the TransitionCaptureState structure, replacing
+# the "tcs_private" field with 3 separate fields. This structure can
+# only be built using MakeTransitionCaptureState(), and PGXN contained
+# no calls to MakeTransitionCaptureState() or uses of the
+# TransitionCaptureState structure.
+
 1d7b02711f70f1ae87be562bca11ea2a9c43e85b
 #
 # For inplace update, send nontransactional invalidations.