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

   # Description
   
   https://issues.apache.org/jira/browse/CAMEL-23163
   
   Align spring-* versions and a number of other third party dependencies to 
the versions in spring-boot-dependencies - these are all limited to patch 
version upgrades with two exceptions.
   
   - hazelcast upgraded from 5.4.0 to 5.5.0 (tested camel-hazecast locally, 
passed all test)
   - infinspan-protostream - infinispan 15.2.6.Final references 
infinispan-protostream 5.0.13.Final rather than 15.0.13.Final 
https://repo1.maven.org/maven2/org/infinispan/infinispan-build-configuration-parent/15.2.6.Final/infinispan-build-configuration-parent-15.2.6.Final.pom.
    I think the protostream 15.0.X versions were convenience releases to match 
numbers up to the infinispan release versions.    Ran tests on camel-infinispan 
locally, passed all tests.     @oscerd does this look okay?
   
   This PR goes along with the PR to camel-spring-boot to upgrade spring-boot 
to 3.5.12 : https://github.com/apache/camel-spring-boot/pull/1722
   
   # 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).
   
   # 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.
   
   
   


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