CAMEL-23584: docs - sync camel-kafka 4.18 / 4.14 upgrade-guide entries to main#23637
Open
oscerd wants to merge 1 commit into
Open
CAMEL-23584: docs - sync camel-kafka 4.18 / 4.14 upgrade-guide entries to main#23637oscerd wants to merge 1 commit into
oscerd wants to merge 1 commit into
Conversation
…s to main The camel-kafka Exchange header constant rename (CAMEL-23584) is being backported to the camel-4.18.x and camel-4.14.x maintenance branches. The version-specific upgrade-guide files on main are the canonical history, so the "potential breaking change" entry for the 4.18 and 4.14 release lines is added here on main (the maintenance-branch backports intentionally omit the upgrade-guide change, per the backport upgrade-guide policy). Adds the "camel-kafka - potential breaking change" section (the kafka.* -> CamelKafka* header constant 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) to both camel-4x-upgrade-guide-4_18.adoc and camel-4x-upgrade-guide-4_14.adoc, matching the entry already present in camel-4x-upgrade-guide-4_21.adoc. Tracker: CAMEL-23577 Reported by Claude Code on behalf of Andrea Cosentino Signed-off-by: Andrea Cosentino <ancosen@gmail.com>
Contributor
|
🌟 Thank you for your contribution to the Apache Camel project! 🌟 🐫 Apache Camel Committers, please review the following items:
|
Contributor
|
🧪 CI tested the following changed modules:
|
apupier
approved these changes
May 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Doc-sync follow-up for 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.adocfiles onmainare the canonical upgrade-guide history across all release lines. The camel-kafka rename is shipping oncamel-4.18.xandcamel-4.14.x, but the maintenance-branch backports intentionally omit the upgrade-guide change (per the backport upgrade-guide policy). This PR adds the matchingpotential breaking changeentry to the4_18and4_14guides onmainso they stay in sync with what those release lines actually ship.What
Adds the
=== camel-kafka - potential breaking changesection to:docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adocdocs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adocThe section mirrors the one already present in
camel-4x-upgrade-guide-4_21.adoc: thekafka.*→CamelKafka*rename table, the symbolic-vs-literal migration note with a before/after example, the Endpoint DSL accessor note, and the cross-transportHeaderFilterStrategybehaviour note.Docs-only change; no code or generated artifacts affected.
Reported by Claude Code on behalf of Andrea Cosentino