davsclaus opened a new pull request, #26348:
URL: https://github.com/apache/camel/pull/26348
## Doc sync follow-up to #26347
CAMEL-24539 was backported to `camel-4.22.x` in #26347, so **4.22.1 is the
first release to carry it**.
On `main`, though, the upgrade note only exists in
`camel-4x-upgrade-guide-4_23.adoc` — the original
PR (#26110) targeted `main` and filed it under 4.23. Since the `4_XX` guides
on `main` are the canonical
history across all release lines, `4_22.adoc` was left out of sync with what
4.22.1 actually ships.
This adds the `camel-openai` section to the *Upgrading from 4.22.0 to
4.22.1* block.
### Two deliberate choices
* **The `4_23.adoc` entry stays.** I checked all 10 existing 4.22.1 entries
on `main` — every one of them
also appears in `4_23.adoc`, so duplication is the established convention
here, not drift.
* **The wording follows the branch, not `4_23.adoc`.** The 4.23 text closes
with *"The chat-completion,
responses, moderation and image operations are unchanged"*, but the
moderation and image operations
don't exist on 4.22.x — they were added later on `main`. This entry lists
only chat-completion and
responses.
### Drive-by, easy to drop
While inserting the section I hit a pre-existing AsciiDoc bug at the
insertion point: `== Upgrading Camel
4.21 to 4.22` had no blank line before it, so Asciidoctor folds the heading
into the preceding paragraph
instead of rendering it. An audit of the file turned up two more (`===
camel-dynamic-router`,
`=== camel-sql - Schema-qualified aggregation repository names`). All three
are fixed here — three blank
lines, no text changes. Happy to split these out if you'd rather keep this
PR to the sync alone.
I diffed the full 4.22.1 section between `main` and `camel-4.22.x`:
`camel-openai` was the only heading
present on the branch and missing from `main`, so this closes the gap rather
than patching one instance of
a wider problem.
_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]
