This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new e014db97c710 chore: fix absolute links to camel.apache.org/security in
MCP docs (#24659)
e014db97c710 is described below
commit e014db97c7108caedbe70a003eb195c679407f71
Author: JiriOndrusek <[email protected]>
AuthorDate: Mon Jul 13 13:32:21 2026 +0200
chore: fix absolute links to camel.apache.org/security in MCP docs (#24659)
Use relative links to avoid camel-website HTML validation failures.
Co-authored-by: Claude Opus 4.6 <[email protected]>
---
docs/user-manual/modules/ROOT/pages/camel-jbang-mcp.adoc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/user-manual/modules/ROOT/pages/camel-jbang-mcp.adoc
b/docs/user-manual/modules/ROOT/pages/camel-jbang-mcp.adoc
index 3acec52f04e7..bb36d38ed70a 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-jbang-mcp.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-jbang-mcp.adoc
@@ -372,7 +372,7 @@ plus prompts that provide structured multi-step workflows.
| `camel_security_advisories`
| Lists the published Apache Camel CVE security advisories (the data behind
- https://camel.apache.org/security/[camel.apache.org/security]), optionally
filtered by Camel version, component
+ link:/security/[camel.apache.org/security]), optionally filtered by Camel
version, component
and severity. Each advisory includes the summary, affected and fixed
versions, mitigation, and a best-effort
verdict on whether the given Camel version is affected. Use it to answer
questions such as "is my Camel 4.10.1
project affected by known CVEs?".
@@ -382,7 +382,7 @@ plus prompts that provide structured multi-step workflows.
The advisory data ships with the Camel catalog bundled in the MCP server,
where it is synced from the official
published Apache Camel security advisories (the sources of
-https://camel.apache.org/security/[camel.apache.org/security]) when Camel is
built — the same way the known
+link:/security/[camel.apache.org/security]) when Camel is built — the same way
the known
releases are synced. Lookups are therefore fully offline, only published
advisories are included, and the data
is as fresh as the Camel version of the MCP server: advisories published after
that release are not included,
so check the web page for the very latest. When the catalog carries no
advisory data the tools report it as
