Upgrade to Camel 4.18.4 - #742
Open
lobtx wants to merge 1 commit into
Open
Conversation
Author
|
Tested this branch against an application of mine (local build):
This application is quite simple: it exposes a REST API that receives a JSON payload and spreads it across multiple queues, which then forward the message to several endpoints (typical ESB). I ran the resulting distribution in a local environment: all features install cleanly, and I verified end-to-end that messages flow through ActiveMQ and my Camel routes as expected. |
jbonofre
self-requested a review
August 27, 2026 06:44
Member
|
Thanks! I would like to merge the other fixes before the update (in order also to test on CI). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Used the tooling to list and apply changes from camel 4.18.4.
I made some fixes due to this upgrade:
camel-google-secret-manager: applied https://issues.apache.org/jira/browse/CAMEL-23729 => protobuf rolled-back to ${protobuf-version} instead of ${protobuf4-version} due to google-cloud-secretmanager downgrade to 2.82.0 in Camel 4.18.3tests: renamed camel headers