oscerd opened a new pull request, #23422: URL: https://github.com/apache/camel/pull/23422
## Summary Docs-only sync of the 4.14 upgrade-guide entry for the `camel-jgroups` header constant rename. [CAMEL-23510](https://issues.apache.org/jira/browse/CAMEL-23510) (PR #23209) renamed the four `JGroupsConstants.HEADER_JGROUPS_*` header string values to follow the `CamelJGroups*` naming convention. The original PR added the upgrade-guide entry to `camel-4x-upgrade-guide-4_21.adoc` on `main`. The backport to `camel-4.14.x` (#23421) places the corresponding entry in `camel-4x-upgrade-guide-4_14.adoc` on the maintenance branch, since the rename ships on that release line. Per the upgrade-guide backport policy in `CLAUDE.md`: > the `docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_XX.adoc` files for ALL versions live on `main` and act as the canonical history across all releases. When a PR is backported to a maintenance branch and adds an upgrade-guide note for that release line, the corresponding entry must ALSO be added to the matching `camel-4x-upgrade-guide-4_XX.adoc` file on `main`. This PR keeps `main`'s 4.14 upgrade guide in sync with what ships on `camel-4.14.x`. ## Changes - `docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc` — add the same `=== camel-jgroups` section already added on `camel-4.14.x` by #23421. Placed in the existing "Upgrading from 4.14.5 to 4.14.6" window, after the existing `=== camel-cxf` section. No code changes; doc-only. ## Test plan - [x] Diff is a 21-line append (one new section). - [x] Section heading style and table format match the existing `=== camel-cxf` entry on the same window. ## Related - Backport PR: #23421 - Original PR (main, 4.21 guide): #23209 --- _Claude Code on behalf of Andrea Cosentino_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
