From ec9f797eaf7b3becb8c96c29e086bb23ae3dd60d Mon Sep 17 00:00:00 2001 From: Andrea Cosentino Date: Fri, 15 May 2026 18:35:54 +0200 Subject: [PATCH] CAMEL-23515: docs - sync camel-nats 4.14 upgrade-guide entry to main The camel-nats HeaderFilterStrategy change is backported to camel-4.14.x (#23255). Per the backport upgrade-guide policy, the matching camel-4x-upgrade-guide-4_14.adoc entry must also live on main as the canonical cross-release history. Signed-off-by: Andrea Cosentino --- .../modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc | 9 +++++++++ 1 file changed, 9 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 cba7f934ab856..3cb824f779ff8 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 @@ -255,3 +255,12 @@ The addresses, privateFor and Topics parameters for camel-web3j have been define The `jobLauncher` and `jobRegistry` is now autowired on the component if there is a single instance pre-configured in the application. This avoids having to wire this into the Camel component or endpoints. + +=== camel-nats + +The default `headerFilterStrategy` is now a new `NatsHeaderFilterStrategy` that filters headers +starting with `Camel` / `camel` (case-insensitive) in both the inbound and outbound directions, +aligning the component with the rest of the Camel component catalog (`camel-kafka`, `camel-mail`, +`camel-coap`, `camel-google-pubsub`, ...). Routes that relied on passing through these header +names from NATS messages can supply a custom `headerFilterStrategy` to restore the previous +behaviour.