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 b644722fd451 CAMEL-23515: docs - sync camel-nats 4.14 upgrade-guide
entry to main
b644722fd451 is described below
commit b644722fd4519fdb95f231826f681081112f2e7b
Author: Andrea Cosentino <[email protected]>
AuthorDate: Mon May 18 09:29:01 2026 +0200
CAMEL-23515: docs - sync camel-nats 4.14 upgrade-guide entry to main
The camel-nats HeaderFilterStrategy change was backported to camel-4.14.x
(#23255, merged). Per the project's backport upgrade-guide policy, the
version-specific camel-4x-upgrade-guide-4_14.adoc lives canonically on main
across all releases. This adds the matching === camel-nats section to that
guide on main so the canonical history does not drift from the maintenance
branch.
Docs-only; no code or build impact.
Closes #23256
---
.../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 cba7f934ab85..3cb824f779ff 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.
