(camel) branch main updated: CAMEL-24464: Sync 4.22 upgrade guide with camel-4.22.x backport (#25983)

[da...@apache.org]

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 8e3e3311b6e1 CAMEL-24464: Sync 4.22 upgrade guide with camel-4.22.x backport (#25983)
8e3e3311b6e1 is described below

commit 8e3e3311b6e1aec781f8600d3ab9283895edf9d0
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Mon Aug 31 22:42:30 2026 +0200

    CAMEL-24464: Sync 4.22 upgrade guide with camel-4.22.x backport (#25983)
    
    Backport #25982 to camel-4.22.x added a camel-exec entry to that
    branch's upgrade guide for the 4.22.0 to 4.22.1 section. Per the
    upgrade-guide policy, main hosts the canonical copy of every
    numbered guide, so mirror the same entry here.
    
    Signed-off-by: Claus Ibsen <cl...@gmail.com>
    Co-authored-by: Claude Sonnet 5 <no...@anthropic.com>
---
 .../modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc      | 12 ++++++++++++
 1 file changed, 12 insertions(+)

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 4eacfff6bdc3..91118ac92bf5 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
@@ -13,6 +13,18 @@ See the xref:camel-upgrade-recipes-tool.adoc[documentation] page for details.
 
 == Upgrading from 4.22.0 to 4.22.1
 
+=== camel-exec
+
+`allowControlHeaders` is now annotated `security = "insecure:dev"`.
+With `camel.main.profile = prod` the default policy for that category is `fail`,
+so an endpoint or component that sets `allowControlHeaders=true` will not start
+unless you relax `camel.security.insecureDevPolicy`.
+
+When the flag is `false` (the default), any remaining `CamelExecCommand*`,
+`CamelExecExitValues`, or `CamelExecUseStderrOnEmptyStdout` headers are ignored
+and a WARN is logged once per exec endpoint. Those headers never overrode the
+URI without the flag; they were just silent before.
+
 === camel-ftp, camel-sftp, camel-ftps, camel-mina-sftp, camel-azure-files, camel-smb
 
 The remote-file consumers now ensure the path resolved for a polled file stays within the directory being