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

davsclaus pushed a commit to branch doc-sync/CAMEL-24359-backport-upgrade-guides
in repository https://gitbox.apache.org/repos/asf/camel.git

commit e902d0b67384ba59a52cd6d791d1d678f673fd9e
Author: Claus Ibsen <[email protected]>
AuthorDate: Thu Aug 6 13:28:16 2026 +0200

    CAMEL-24359: doc-sync backported upgrade-guide entries to main
    
    Add the camel-atmosphere-websocket header rename upgrade-guide entries
    for 4.18.4 and 4.14.9, syncing back from the backport PRs #25382 and
    #25383.
    
    Co-Authored-By: Claude Opus 4.6 <[email protected]>
    Signed-off-by: Claus Ibsen <[email protected]>
---
 .../ROOT/pages/camel-4x-upgrade-guide-4_14.adoc     | 21 +++++++++++++++++++++
 .../ROOT/pages/camel-4x-upgrade-guide-4_18.adoc     | 21 +++++++++++++++++++++
 2 files changed, 42 insertions(+)

diff --git 
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc 
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
index fc33b266b7dd..4ecedb7cc6da 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
@@ -53,6 +53,27 @@ filtering performed by other components.
 
 Ordinary application headers are unaffected.
 
+=== camel-atmosphere-websocket - potential breaking change
+
+The Exchange header constants in `WebsocketConstants` have been renamed to 
follow the
+Camel naming convention used across the rest of the component catalog. The 
Java field
+names are unchanged; only the header string values have changed:
+
+[options="header"]
+|===
+| Constant | Previous value | New value
+| `WebsocketConstants.CONNECTION_KEY`      | `websocket.connectionKey`      | 
`CamelAtmosphereWebsocketConnectionKey`
+| `WebsocketConstants.CONNECTION_KEY_LIST` | `websocket.connectionKey.list` | 
`CamelAtmosphereWebsocketConnectionKeyList`
+| `WebsocketConstants.SEND_TO_ALL`         | `websocket.sendToAll`          | 
`CamelAtmosphereWebsocketSendToAll`
+| `WebsocketConstants.EVENT_TYPE`          | `websocket.eventType`          | 
`CamelAtmosphereWebsocketEventType`
+| `WebsocketConstants.ERROR_TYPE`          | `websocket.errorType`          | 
`CamelAtmosphereWebsocketErrorType`
+|===
+
+Routes that reference the constant symbolically (for example
+`setHeader(WebsocketConstants.CONNECTION_KEY, ...)`) continue to work without 
changes.
+Routes that set the header by its literal string value must be updated to use 
the new
+value.
+
 == Upgrading from 4.14.3 to 4.14.8
 
 === camel-jackson - potential breaking change
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 187a378e27b8..1e2dcc1ac7a1 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
@@ -89,6 +89,27 @@ filtering performed by other components.
 
 Ordinary application headers are unaffected.
 
+=== camel-atmosphere-websocket - potential breaking change
+
+The Exchange header constants in `WebsocketConstants` have been renamed to 
follow the
+Camel naming convention used across the rest of the component catalog. The 
Java field
+names are unchanged; only the header string values have changed:
+
+[options="header"]
+|===
+| Constant | Previous value | New value
+| `WebsocketConstants.CONNECTION_KEY`      | `websocket.connectionKey`      | 
`CamelAtmosphereWebsocketConnectionKey`
+| `WebsocketConstants.CONNECTION_KEY_LIST` | `websocket.connectionKey.list` | 
`CamelAtmosphereWebsocketConnectionKeyList`
+| `WebsocketConstants.SEND_TO_ALL`         | `websocket.sendToAll`          | 
`CamelAtmosphereWebsocketSendToAll`
+| `WebsocketConstants.EVENT_TYPE`          | `websocket.eventType`          | 
`CamelAtmosphereWebsocketEventType`
+| `WebsocketConstants.ERROR_TYPE`          | `websocket.errorType`          | 
`CamelAtmosphereWebsocketErrorType`
+|===
+
+Routes that reference the constant symbolically (for example
+`setHeader(WebsocketConstants.CONNECTION_KEY, ...)`) continue to work without 
changes.
+Routes that set the header by its literal string value must be updated to use 
the new
+value.
+
 == Upgrading from 4.18.1 to 4.18.3
 
 === camel-jackson - potential breaking change

Reply via email to