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

   # Description
   
   Follow-up to a [review comment on 
#24322](https://github.com/apache/camel/pull/24322#pullrequestreview-4702333394):
 the CSS-backed TUI theme / F4-toggle note landed in 
`camel-4x-upgrade-guide-4_21.adoc`, but `main` is `4.22.0-SNAPSHOT`, so the 
feature actually ships in 4.22. This moves the note to 
`camel-4x-upgrade-guide-4_22.adoc`, placing it next to the related 
`--theme=dark|light` flag and F2 *Settings…* entries already documented there.
   
   While moving it, the referenced config file name was updated from 
`.camel-jbang-user.properties` to `.camel-cli.properties`, since that rename 
(CAMEL-23867) is already on `main` and the old name would have been stale in 
the 4.22 guide.
   
   # Target
   
   - [x] I checked that the commit is targeting the correct branch (Camel 4 
uses the `main` branch)
   
   # Tracking
   - [x] If this is a large change, bug fix, or code improvement, I checked 
there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for 
the change (usually before you start working on it).
   
   <!--
   # *Note*: trivial changes like, typos, minor documentation fixes and other 
small items do not require a JIRA issue. In this case your pull request should 
address just this issue, without pulling in other changes.
   -->
   
   # Apache Camel coding standards and style
   
   - [x] I checked that each commit in the pull request has a meaningful 
subject line and body.
   
   - [x] I have run `mvn clean install -DskipTests` locally from root folder 
and I have committed all auto-generated changes.
   
   # AI-assisted contributions
   
   - [x] If this PR includes AI-generated code, commits have proper 
co-authorship attribution (e.g., `Co-authored-by` trailers) and the PR 
description identifies the AI tool used.
   
   _This PR was created with Claude Code on behalf of Adriano Machado 
(@ammachado)._


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