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 7a46dbbca88f CAMEL-24084: Sync knative structured-mode CloudEvent
header-filtering upgrade notes to 4_18 and 4_14 guides (#24768)
7a46dbbca88f is described below
commit 7a46dbbca88fba647c89da86ed172251c4622fc3
Author: Andrea Cosentino <[email protected]>
AuthorDate: Thu Jul 16 10:58:10 2026 +0200
CAMEL-24084: Sync knative structured-mode CloudEvent header-filtering
upgrade notes to 4_18 and 4_14 guides (#24768)
The camel-knative structured-mode CloudEvent header-filtering change
(CAMEL-24084) is backported to 4.18.4 and
4.14.9. Per the backport upgrade-guide policy, add the matching notes to
the 4_18 and 4_14 upgrade guides on main
(the 4_22 note ships with the main fix PR).
Co-authored-by: Claude Opus 4.8 (1M context) <[email protected]>
---
.../modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc | 11 +++++++++++
.../modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 11 +++++++++++
2 files changed, 22 insertions(+)
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
index 34e0f9caf7d3..0f30ccf759d9 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
@@ -23,6 +23,17 @@ the message, consistent with the inbound header filtering
already performed by t
Ordinary application headers are unaffected. If a route relied on `Camel*`
headers being propagated from the MIME
content, set them explicitly after unmarshalling.
+=== camel-knative - structured-mode CloudEvent header filtering
+
+When consuming a CloudEvent in structured content mode
(`application/cloudevents+json`), the Knative component now
+applies a `HeaderFilterStrategy` to the event fields (extensions) mapped from
the payload onto the Camel message.
+Camel-internal headers (the `Camel*` namespace, matched case-insensitively)
present as structured-event fields are
+no longer mapped onto the message, consistent with the inbound header
filtering already performed on the binary
+content-mode / HTTP header path.
+
+Ordinary CloudEvent extension attributes are unaffected. If a route relied on
`Camel*`-named fields being
+propagated from the structured payload, set them explicitly after consuming
the event.
+
== Upgrading from 4.14.3 to 4.14.8
=== camel-jackson - potential breaking change
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 c350992a215c..454134a14669 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
@@ -50,6 +50,17 @@ the message, consistent with the inbound header filtering
already performed by t
Ordinary application headers are unaffected. If a route relied on `Camel*`
headers being propagated from the MIME
content, set them explicitly after unmarshalling.
+=== camel-knative - structured-mode CloudEvent header filtering
+
+When consuming a CloudEvent in structured content mode
(`application/cloudevents+json`), the Knative component now
+applies a `HeaderFilterStrategy` to the event fields (extensions) mapped from
the payload onto the Camel message.
+Camel-internal headers (the `Camel*` namespace, matched case-insensitively)
present as structured-event fields are
+no longer mapped onto the message, consistent with the inbound header
filtering already performed on the binary
+content-mode / HTTP header path.
+
+Ordinary CloudEvent extension attributes are unaffected. If a route relied on
`Camel*`-named fields being
+propagated from the structured payload, set them explicitly after consuming
the event.
+
== Upgrading from 4.18.1 to 4.18.3
=== camel-jackson - potential breaking change
