oscerd opened a new pull request, #23509:
URL: https://github.com/apache/camel/pull/23509

   ## Backport of #23474
   
   Cherry-pick of #23474 onto `camel-4.18.x`.
   
   - **Original PR:** apache/camel#23474 — *CAMEL-23590: camel-milo - align 
Exchange header constant names with Camel naming convention*
   - **Squash merge cherry-picked:** `09d38da3ef2`
   - **Target branch:** `camel-4.18.x`
   - **Original author:** @oscerd
   - **camel-4.14.x:** N/A — `camel-milo` does not exist on the 4.14 line (the 
component was removed and later reinstated).
   
   ### Manual adjustments during cherry-pick
   
   - **Upgrade-guide entry moved** from `camel-4x-upgrade-guide-4_21.adoc` 
(does not
     exist on this branch) to `camel-4x-upgrade-guide-4_18.adoc`, preserving the
     full content including the `- potential breaking change` flag. The matching
     `4_18.adoc` entry on `main` should be synced in a follow-up PR per
     CLAUDE.md's backport upgrade-guide policy.
   - **Regenerated** component metadata, catalog, and endpoint DSL using
     4.18.x's generators (full reactor build, `-DskipTests`).
   
   ### Change summary
   
   Renames `MiloConstants.HEADER_AWAIT` header string value from `"await"` to
   `"CamelMiloAwait"`. The Java field name is unchanged so routes referencing 
the
   constant symbolically continue to work; routes using the literal string value
   must be updated. Also updates the two tests that set the header by literal
   value, and the generated endpoint DSL header accessor (`await()` → 
`miloAwait()`).
   `MiloConstants.HEADER_NODE_IDS` was already `Camel`-prefixed and is 
unchanged.
   
   JIRA: https://issues.apache.org/jira/browse/CAMEL-23590
   
   ---
   _Backport prepared 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]

Reply via email to