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

   ## Backport of #26110 — replaces #26337
   
   Cherry-pick of `bd89b383fe41441f0165cc7d228da011c34eaf5a` to `camel-4.22.x`.
   
   ### Why a new PR
   
   #26337 (the bot backport) fails CI on both JDK 17 and JDK 25, in the *"There 
are uncommitted changes"*
   step rather than in a test. Its automatic conflict resolution left a **stray 
duplicate `/**`** in the
   generated endpoint DSL:
   
   ```java
           }
           /**
           /**
            * The complete OpenAI embeddings response object.
   ```
   
   `mvn -Pregen` removes that line, so the working tree is dirty after 
regeneration and the check exits 1.
   Since the branch belongs to the backport bot, this PR carries the corrected 
cherry-pick instead
   (original author preserved).
   
   ### Verification
   
   * Removed the stray line, then rebuilt `camel-openai`, 
`catalog/camel-catalog` and `dsl/camel-endpointdsl`
     with the build cache disabled — the regenerated sources are byte-identical 
to what is committed here,
     and `components/camel-ai/camel-openai/.../openai.json` + the catalog JSON 
needed no changes.
   * `components/camel-ai/camel-openai`: 28 tests pass 
(`OpenAIEmbeddings*Test`, `OpenAIAudio*Test`), including
     the new `CamelOpenAIEmbeddingsResponse` assertions.
   
   ### Note for the release
   
   The upgrade-guide entry lands in `camel-4x-upgrade-guide-4_22.adoc` (4.22.1 
is the first release on this
   line to carry the change). On `main` the original commit added it to 
`camel-4x-upgrade-guide-4_23.adoc`;
   per the backport upgrade-guide policy, `main`'s `4_22.adoc` should get the 
same entry in a follow-up doc-sync.
   
   _Claude Code on behalf of @davsclaus_
   


-- 
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