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

   Adds the 4.23 upgrade guide entries for the camel-spring-boot changes that 
are landing under these tickets, next to the camel-spring-boot entries already 
present for the release:
   
   - [CAMEL-24498](https://issues.apache.org/jira/browse/CAMEL-24498) 
camel-observability-services-starter narrows its injected defaults 
(apache/camel-spring-boot#1927)
   - [CAMEL-24500](https://issues.apache.org/jira/browse/CAMEL-24500) 
camel-debug-starter no longer opens a JMX connector by default 
(apache/camel-spring-boot#1928)
   - [CAMEL-24592](https://issues.apache.org/jira/browse/CAMEL-24592) health 
check stack traces moved to the full exposure level 
(apache/camel-spring-boot#1929)
   - [CAMEL-24593](https://issues.apache.org/jira/browse/CAMEL-24593) 
camel-platform-http-starter deletes multipart uploads when the exchange 
completes (apache/camel-spring-boot#1934)
   - [CAMEL-24577](https://issues.apache.org/jira/browse/CAMEL-24577) 
camel-platform-http-starter path variables follow the matched path 
(apache/camel-spring-boot#1932)
   - [CAMEL-24505](https://issues.apache.org/jira/browse/CAMEL-24505) 
camel-micrometer-starter bounds the uri tag (apache/camel-spring-boot#1933)
   - [CAMEL-24506](https://issues.apache.org/jira/browse/CAMEL-24506) 
camel-jasypt-starter defaults to PBEWITHHMACSHA256ANDAES_256 
(apache/camel-spring-boot#1931)
   - [CAMEL-24501](https://issues.apache.org/jira/browse/CAMEL-24501) starter 
configuration options that cannot be bound are reported 
(apache/camel-spring-boot#1935)
   
   Documentation only. Each entry should be merged together with, or after, the 
PR it describes; entries for PRs that end up not merged for 4.23 should be 
dropped from this one.
   
   _Claude Code on behalf of Croway_
   


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