oscerd opened a new pull request, #23637: URL: https://github.com/apache/camel/pull/23637
Doc-sync follow-up for [CAMEL-23584](https://issues.apache.org/jira/browse/CAMEL-23584) (camel-kafka header constant rename, merged in #23602 and backported in #23629 / #23632). ## Why The version-specific `camel-4x-upgrade-guide-4_XX.adoc` files on `main` are the canonical upgrade-guide history across all release lines. The camel-kafka rename is shipping on `camel-4.18.x` and `camel-4.14.x`, but the maintenance-branch backports intentionally **omit** the upgrade-guide change (per the backport upgrade-guide policy). This PR adds the matching `potential breaking change` entry to the `4_18` and `4_14` guides on `main` so they stay in sync with what those release lines actually ship. ## What Adds the `=== camel-kafka - potential breaking change` section to: - `docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc` - `docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc` The section mirrors the one already present in `camel-4x-upgrade-guide-4_21.adoc`: the `kafka.*` → `CamelKafka*` rename table, the symbolic-vs-literal migration note with a before/after example, the Endpoint DSL accessor note, and the cross-transport `HeaderFilterStrategy` behaviour note. Docs-only change; no code or generated artifacts affected. _Reported by 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]
