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-quarkus.git


The following commit(s) were added to refs/heads/main by this push:
     new 24b53fc62e ci: use relative links in security-model.adoc (#8661)
24b53fc62e is described below

commit 24b53fc62e14d7e055bc63ae618b048eb08aec9a
Author: Andrea Cosentino <[email protected]>
AuthorDate: Sat May 16 12:23:46 2026 +0200

    ci: use relative links in security-model.adoc (#8661)
    
    The Camel Quarkus security model user-guide page linked the camel.apache.org
    security page with absolute https://camel.apache.org/... URLs. 
camel-website's
    check:html step enforces the camel/relative-links rule and fails on in-site
    absolute links (2 errors for this page), turning every camel-website pull
    request red.
    
    Convert the two in-site links to root-relative link:/security/, matching
    apache/camel core security-model.adoc (fixed the same way in 
apache/camel#23224).
    The [email protected] email reference is intentionally left
    unchanged. Documentation-only; same link target, rendered relative.
    
    Signed-off-by: Andrea Cosentino <[email protected]>
    Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>
---
 docs/modules/ROOT/pages/user-guide/security-model.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/modules/ROOT/pages/user-guide/security-model.adoc 
b/docs/modules/ROOT/pages/user-guide/security-model.adoc
index f2537ede11..9c1e4e5772 100644
--- a/docs/modules/ROOT/pages/user-guide/security-model.adoc
+++ b/docs/modules/ROOT/pages/user-guide/security-model.adoc
@@ -80,7 +80,7 @@ component author guidance]:
 
 The Apache Camel Quarkus project uses the standard ASF vulnerability reporting 
process:
 
-* Read https://camel.apache.org/security/[Apache Camel Security] for 
instructions.
+* Read link:/security/[Apache Camel Security] for instructions.
 * Email `[email protected]` with a description, affected 
versions, and a proof of
   concept that demonstrates the trust-boundary breach.
 * Do **not** file a public GitHub issue, Jira ticket, open a public pull 
request, post on a mailing
@@ -101,5 +101,5 @@ this document.
 * https://quarkus.io/security/[Quarkus Security Policy] - security policy for 
the Quarkus framework.
 * https://quarkus.io/guides/security[Quarkus Security Guides] - guides on 
securing Quarkus
   applications.
-* https://camel.apache.org/security/[Apache Camel Security] - public advisory 
index and reporting
+* link:/security/[Apache Camel Security] - public advisory index and reporting
   process.

Reply via email to