This is an automated email from the ASF dual-hosted git repository. luigidemasi pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/camel.git
commit ab8476824a79e630a4b6a0bc20906100c3012aca Author: Luigi De Masi <[email protected]> AuthorDate: Sat Nov 14 08:49:47 2026 +0100 CAMEL-26926: Document runtime catalog fix for 4.22.3 and 4.18.6 Co-authored-by: Codex <[email protected]> Signed-off-by: Luigi De Masi <[email protected]> --- .../ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 22 ++++++++++++++++++++++ .../ROOT/pages/camel-4x-upgrade-guide-4_22.adoc | 19 +++++++++++++++++++ 2 files changed, 41 insertions(+) diff --git a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc index 462073af8c6f..16021bbafe8e 100644 --- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc +++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc @@ -909,6 +909,28 @@ A Netty consumer using `sslContextParameters` now uses the client authentication when the `needClientAuth` option is not enabled. Previously `needClientAuth=false` (the default) turned the client authentication off. +=== camel-jbang - runtime catalogs use the selected Camel version + +Spring Boot and Quarkus catalogs now report the resolved Camel core version and read EIP/model schemas from that +version's catalog. Previously, they could combine the selected runtime's component schemas with the running CLI or +MCP server's newer model schemas. A model absent from the selected catalog now remains absent. +Runtime dependency coordinates still use the selected Spring Boot or Camel Quarkus version. + +Versioned Main catalogs also report the selected version: `DefaultCamelCatalog.getCatalogVersion()` now honors +the installed version manager instead of always reporting the built-in version. + +A Quarkus BOM must identify both `org.apache.camel:camel-catalog` and +`org.apache.camel.quarkus:camel-quarkus-catalog`. If either version or the selected catalog cannot be resolved, +catalog loading fails instead of returning the running server's catalog. + +Spring Boot retains its existing fallback: if downloading `org.apache.camel:camel-catalog` for the requested +version fails, it tries the running CLI's Camel version. The catalog reports the core version actually resolved. + +For Spring Boot, `camel export` and `camel run` without an explicit `--camel-version` now use the resolved core +catalog version for Camel core dependencies in the generated project. For example, `--camel-spring-boot-version=4.8.0` +uses Camel 4.8.0 instead of the running CLI's version when that catalog is available. Set `--camel-version` explicitly +to retain a different core dependency version. + == Upgrading from 4.18.4 to 4.18.5 === camel-azure-eventhubs diff --git a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc index fb76e000c72c..2b1de60e6ac8 100644 --- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc +++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc @@ -833,6 +833,25 @@ thread (for example, after an aggregator). A commit called after the partition was revoked from the consumer is not made. It would move back the offset that the new owner of the partition committed. +=== camel-jbang - runtime catalogs use the selected Camel version + +Spring Boot and Quarkus catalogs now report the resolved Camel core version and read EIP/model schemas from that +version's catalog. Previously, they could combine the selected runtime's component schemas with the running CLI or +MCP server's newer model schemas. A model absent from the selected catalog now remains absent. +Runtime dependency coordinates still use the selected Spring Boot or Camel Quarkus version. + +A Quarkus BOM must identify both `org.apache.camel:camel-catalog` and +`org.apache.camel.quarkus:camel-quarkus-catalog`. If either version or the selected catalog cannot be resolved, +catalog loading fails instead of returning the running server's catalog. + +Spring Boot retains its existing fallback: if downloading `org.apache.camel:camel-catalog` for the requested +version fails, it tries the running CLI's Camel version. The catalog reports the core version actually resolved. + +For Spring Boot, `camel export` and `camel run` without an explicit `--camel-version` now use the resolved core +catalog version for Camel core dependencies in the generated project. For example, `--camel-spring-boot-version=4.8.0` +uses Camel 4.8.0 instead of the running CLI's version when that catalog is available. Set `--camel-version` explicitly +to retain a different core dependency version. + == Upgrading from 4.22.1 to 4.22.2 === camel-lra - only an LRA hosted by the configured coordinator is joined
