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 e889ce0267d4ef5d15a131f30b6f4f3be35ac991..e4a7770611a6ec1afda9792f247092df11d38c40 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.
 
+c5824536e7ca3c5ef5a9db59bd36c4e6beb23f51
+#
+# Fix trigger transition table capture for MERGE in CTE queries.
+# 2026-01-24 11:30:51 +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.
+
 05d605b6c69f0276ae091ced1ed9082963052550
 #
 # For inplace update, send nontransactional invalidations.