Repository navigation
Conversation
oscerd
approved these changes
Nov 18, 2026
Contributor
Author
|
The Integration Tests fail because of a regression in the Camel 4.24.0-SNAPSHOT CLI, not because of this PR. The snapshot itself runs fine: each integration starts as Apache Camel (JBang) 4.24.0-SNAPSHOT and reaches Running. The failure is at the end of each test. Citrus runs The fix is CAMEL-27149, apache/camel#30321. I'll rerun the tests here once it is in a published snapshot, and hold the merge until then. Claude Code on behalf of Claus Ibsen |
This was referenced Nov 18, 2026
Open
The parent camel-dependencies and camel.version move from 4.23.0 to 4.24.0-SNAPSHOT, so that the Kamelets can use what Camel main adds for 4.24, such as the schema registry options of camel-kafka (CAMEL-27130) for the Kafka Kamelets (apache#3183). The Apache snapshot repository is already configured. The catalog SBOM is regenerated with the Camel components at 4.24.0-SNAPSHOT. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
davsclaus
force-pushed
the
quick-fix/camel-4.24.0-snapshot
branch
from
November 18, 2026 09:40
0bc9383 to
b366aed
Compare
This was referenced Nov 18, 2026
Contributor
Author
Contributor
Author
|
Merged as part of #3202. Claude Code on behalf of Claus Ibsen |
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.
The catalog now builds against Camel 4.24.0-SNAPSHOT instead of 4.23.0:
camel-dependenciesis now 4.24.0-SNAPSHOT;camel.versionis now 4.24.0-SNAPSHOT.Why: the Kamelets can then use what Camel
mainadds for 4.24. The next step is the schema registry options of camel-kafka (CAMEL-27130, apache/camel#30295, merged) on the Kafka Kamelets (#3183, #3144). The build checks every Kamelet option against the Camel catalog, so a Kamelet cannot use those options while the catalog builds against 4.23.0.What else changes:
Catalog Dependency Scanalready scanscamel:components at the newest Camel release, as OSV has no data for a SNAPSHOT.camel.version, which is now the 4.24.0-SNAPSHOT CLI from the snapshot repository.Move to 4.24.0 when Camel 4.24.0 is released.
Merged together with #3136. On 4.24 the
jacksondata format is the Jackson 3 one whenever camel-jackson3 is on the classpath, as it is in Camel JBang. So the Kamelets must move to Jackson 3, which #3136 does. The second CI run failed 11 Citrus tests on this:json-deserialize-actionand the field actions, the avro and protobuf actions, and the Jira source. The startup failure is a Camel bug, CAMEL-27164 (apache/camel#30338). Even with that fixed, the Kamelets that name the Jackson 2JsonNodefail on the first message. #3136 is to be rebased on this branch, so CI runs both, and they merge together once it is green.Verification:
./mvnw clean installpassed twice, the first time with-DskipTests.CommonIT#timerpassed, with the CLI running as Apache Camel 4.24.0-SNAPSHOT.camel stopregression:camel stop <pid>of the process that launched an integration exited with code 3, and Citrus stops integrations that way. CAMEL-27149 (CAMEL-27149: camel-jbang - camel stop <pid> of the process that launched an integration stops that integration camel#30321) fixed it, and the snapshot of 2026-11-18 09:10 UTC contains the fix. This branch was rebased ontomainafter that, so CI runs the tests again with the fixed CLI.Claude Code on behalf of Claus Ibsen
🤖 Generated with Claude Code