(camel) branch main updated: CAMEL-23461: docs - sync 4.18 upgrade-guide entry to main for camel-aws-bedrock (#23176)

[ac...@apache.org]

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

oscerd 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 3c61056b2b09 CAMEL-23461: docs - sync 4.18 upgrade-guide entry to main for camel-aws-bedrock (#23176)
3c61056b2b09 is described below

commit 3c61056b2b091c0bfde09388f97672d47508a826
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Wed May 13 10:20:56 2026 +0200

    CAMEL-23461: docs - sync 4.18 upgrade-guide entry to main for camel-aws-bedrock (#23176)
    
    Add the camel-aws-bedrock upgrade-guide entry to main's
    camel-4x-upgrade-guide-4_18.adoc to match the entry shipped on the
    camel-4.18.x branch via PR #23161 (squash 540bd6b/e22edbb5).
    
    Per the project's backport upgrade-guide policy, the
    camel-4x-upgrade-guide-4_XX.adoc files for ALL versions live on main
    and act as the canonical history across all release lines. Without
    this sync, main's 4.18 upgrade guide drifts out of sync with what is
    actually shipping on the camel-4.18.x maintenance branch.
    
    Co-authored-by: Claude Opus 4.7 (1M context) <no...@anthropic.com>
---
 .../modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc        | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
index afe73be91679..631494f8ed4a 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
@@ -73,6 +73,16 @@ sjms:queue:foo?objectMessageEnabled=true
 sjms2:queue:foo?objectMessageEnabled=true
 ----
 
+=== camel-aws-bedrock
+
+The `applyGuardrail` producer operation now reads the guardrail identifier from a new dedicated header
+`CamelAwsBedrockGuardrailIdentifier` (constant `BedrockConstants.GUARDRAIL_IDENTIFIER`, typed `String`)
+instead of `CamelAwsBedrockGuardrailConfig`. The `CamelAwsBedrockGuardrailConfig` header is typed
+`GuardrailConfiguration` and is reserved for the `converse` and `converseStream` operations; the
+previous code path silently produced `null` whenever a route mixed `converse` and `applyGuardrail`
+calls. If you were not setting the guardrail identifier via header, the endpoint-level
+`guardrailIdentifier` option continues to work without changes.
+
 === camel-hazelcast
 
 Hazelcast instances created and managed by Camel (when no user-supplied