Skip to content

CAMEL-23515: docs - sync camel-nats 4.18 upgrade-guide entry to main#23252

Open
oscerd wants to merge 1 commit into
apache:mainfrom
oscerd:docs/CAMEL-23515-upgrade-guide-4_18-sync
Open

CAMEL-23515: docs - sync camel-nats 4.18 upgrade-guide entry to main#23252
oscerd wants to merge 1 commit into
apache:mainfrom
oscerd:docs/CAMEL-23515-upgrade-guide-4_18-sync

Conversation

@oscerd
Copy link
Copy Markdown
Contributor

@oscerd oscerd commented May 15, 2026

Summary

Doc-sync follow-up for the camel-nats HeaderFilterStrategy change.

Per the project's backport upgrade-guide policy, the version-specific
camel-4x-upgrade-guide-4_XX.adoc files live canonically on main across
all releases. The 4.18.x backport (#23250) adds the camel-nats header-filter
note to camel-4x-upgrade-guide-4_18.adoc on the maintenance branch; this PR
adds the matching entry to camel-4x-upgrade-guide-4_18.adoc on main so the
canonical history does not drift.

Change

Adds a === camel-nats section to camel-4x-upgrade-guide-4_18.adoc
documenting the new default NatsHeaderFilterStrategy.

Docs-only; no code or build impact.

Note: camel-4x-upgrade-guide-4_18.adoc on main currently has no
=== camel-nats section at all, so the pre-existing 4.18.x JetStream
pull-fix note is also missing from main's copy (separate pre-existing
drift, intentionally left out of scope here to keep this PR focused).

JIRA: https://issues.apache.org/jira/browse/CAMEL-23515

Claude Code on behalf of Andrea Cosentino

The camel-nats HeaderFilterStrategy change is backported to camel-4.18.x
(apache#23250). Per the backport upgrade-guide policy, the matching
camel-4x-upgrade-guide-4_18.adoc entry must also live on main as the
canonical cross-release history.

Signed-off-by: Andrea Cosentino <ancosen@gmail.com>
@github-actions
Copy link
Copy Markdown
Contributor

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

  • First-time contributors require MANUAL approval for the GitHub Actions to run
  • You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
  • You can label PRs using skip-tests and test-dependents to fine-tune the checks executed by this PR.
  • Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

@github-actions github-actions Bot added the docs label May 15, 2026
@github-actions
Copy link
Copy Markdown
Contributor

🧪 CI tested the following changed modules:

  • docs

⚙️ View full build and test results

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants