This is an automated email from the ASF dual-hosted git repository. davsclaus pushed a commit to branch quick-fix/pqc-xref-fragment in repository https://gitbox.apache.org/repos/asf/camel.git
commit 7eb07b35b51570335d58070f97b05a5c4a776148 Author: Claus Ibsen <[email protected]> AuthorDate: Sat Jun 20 11:22:00 2026 +0200 chore: Fix fragment anchor in pqc-dataformat xref to pqc-hybrid Antora generates section anchors with underscores and leading underscore, not hyphens. Co-Authored-By: Claude <[email protected]> Signed-off-by: Claus Ibsen <[email protected]> --- components/camel-pqc/src/main/docs/pqc-dataformat.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/components/camel-pqc/src/main/docs/pqc-dataformat.adoc b/components/camel-pqc/src/main/docs/pqc-dataformat.adoc index 8e6e6165463b..8648b0f85e78 100644 --- a/components/camel-pqc/src/main/docs/pqc-dataformat.adoc +++ b/components/camel-pqc/src/main/docs/pqc-dataformat.adoc @@ -39,7 +39,7 @@ This approach provides **defense-in-depth**: even if the symmetric algorithm is == Wire Format -Since Camel 4.19, the PQC DataFormat uses wire format v2 which includes magic bytes, version, and algorithm identifiers (see xref:others:pqc-hybrid.adoc#wire-format-v2-and-algorithm-identification[Wire Format v2 and Algorithm Identification]). The v1 format `[4 bytes: encapsulation length][N bytes: encapsulation][M bytes: encrypted data]` is still accepted on input for backward compatibility. +Since Camel 4.19, the PQC DataFormat uses wire format v2 which includes magic bytes, version, and algorithm identifiers (see xref:others:pqc-hybrid.adoc#_wire_format_v2_and_algorithm_identification[Wire Format v2 and Algorithm Identification]). The v1 format `[4 bytes: encapsulation length][N bytes: encapsulation][M bytes: encrypted data]` is still accepted on input for backward compatibility. The v2 encrypted message format is:
