This is an automated email from the ASF dual-hosted git repository.

oscerd pushed a commit to branch camel-4.18.x
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/camel-4.18.x by this push:
     new d75d0cfe199d CAMEL-23526: docs - flag camel-cxf 4.18 upgrade-guide 
entry as potential breaking change (#23461)
d75d0cfe199d is described below

commit d75d0cfe199da07fa275f335913cf28e0591e8aa
Author: Andrea Cosentino <[email protected]>
AuthorDate: Fri May 22 11:41:36 2026 +0200

    CAMEL-23526: docs - flag camel-cxf 4.18 upgrade-guide entry as potential 
breaking change (#23461)
    
    Signed-off-by: Andrea Cosentino <[email protected]>
---
 docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc 
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
index 24dd5660cdc7..50fcc25eed7b 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
@@ -415,7 +415,7 @@ component with the rest of the Camel component catalog. 
Routes that relied on re
 header names on inbound SNS messages can supply a custom 
`headerFilterStrategy` to restore the
 previous behaviour.
 
-=== camel-cxf
+=== camel-cxf - potential breaking change
 
 The Exchange header constants in `CxfConstants` (module `camel-cxf-common`, 
shared
 by `camel-cxf` and `camel-cxfrs`) have been renamed to follow the Camel naming

Reply via email to