This is an automated email from the ASF dual-hosted git repository.

github-actions[bot] pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-k.git


The following commit(s) were added to refs/heads/main by this push:
     new f9582724f chore: nightly automatic updates
f9582724f is described below

commit f9582724f174bbd6dad188388b58e5398fc4bc0f
Author: github-actions[bot] 
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Fri Nov 13 23:36:39 2026 +0000

    chore: nightly automatic updates
---
 README.adoc                         | 2 +-
 docs/modules/traits/pages/keda.adoc | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.adoc b/README.adoc
index 681f388e6..3035ae801 100644
--- a/README.adoc
+++ b/README.adoc
@@ -7,7 +7,7 @@ 
image:https://img.shields.io/github/license/openshift/origin.svg?maxAge=2592000[
 image:https://godoc.org/github.com/apache/camel-k?status.svg["GoDoc";, 
link="https://godoc.org/github.com/apache/camel-k";]
 image:https://github.com/apache/camel-k/workflows/build/badge.svg["Build";, 
link="https://github.com/apache/camel-k/actions/workflows/build.yml";]
 
image:https://github.com/apache/camel-k/actions/workflows/nightly-release.yml/badge.svg["Nightly
 releases", 
link="https://github.com/apache/camel-k/actions/workflows/nightly-release.yml";]
-image:https://img.shields.io/badge/Coverage-65.0-yellow.svg["Code coverage"]
+image:https://img.shields.io/badge/Coverage-65.1-yellow.svg["Code coverage"]
 image:https://img.shields.io/badge/zulip-join_chat-brightgreen.svg["Chat on 
Zulip", link="https://camel.zulipchat.com";]
 
 Apache Camel K is a lightweight integration framework built from **Apache 
Camel** that runs natively on Kubernetes and is specifically designed for 
serverless and microservice architectures. Users of `Camel K` can instantly run 
integration code written in Camel DSL on their preferred **Cloud** provider.
diff --git a/docs/modules/traits/pages/keda.adoc 
b/docs/modules/traits/pages/keda.adoc
index ba1e2628f..de5abacf5 100644
--- a/docs/modules/traits/pages/keda.adoc
+++ b/docs/modules/traits/pages/keda.adoc
@@ -81,4 +81,4 @@ Automatic discovery currently supports the following Camel 
components:
 * `pulsar`: creates an Apache Pulsar trigger from the topic in the endpoint 
URI and the `subscriptionName` option (Camel's default `subs` when it is not 
set). When the service URL (`serviceUrl` option or 
`camel.component.pulsar.service-url` property) uses the `pulsar://` scheme, 
`adminURL` is set to `http://<host>:8080`; for TLS or a custom admin port, set 
it with `keda.autoMetadata`. See the 
https://keda.sh/docs/latest/scalers/pulsar/[KEDA Apache Pulsar scaler] 
documentation for the ava [...]
 * `spring-rabbitmq`: creates a RabbitMQ trigger whose `queueName` is the 
`queues` value of the endpoint URI, when it names a single queue. The broker 
address is not part of the URI: a `host` endpoint parameter, when present, is 
used as the trigger `host` as is; otherwise set `host`, together with `mode` 
and `value`, with `keda.autoMetadata`. See the 
https://keda.sh/docs/latest/scalers/rabbitmq-queue/[KEDA RabbitMQ Queue scaler] 
documentation for the available trigger metadata.
 
-Unsupported Camel components do not produce an automatically discovered 
trigger. You can still configure their KEDA triggers explicitly with 
`keda.triggers`.
\ No newline at end of file
+Unsupported Camel components do not produce an automatically discovered 
trigger. You can still configure their KEDA triggers explicitly with 
`keda.triggers`.

Reply via email to