Skip to content

CAMEL-23630: Document camel-dapr 4.18.x consumer header change in 4.18 upgrade guide#23891

Merged
oscerd merged 1 commit into
apache:mainfrom
oscerd:CAMEL-23630-doc-sync-4.18-guide-to-main
Jun 10, 2026
Merged

CAMEL-23630: Document camel-dapr 4.18.x consumer header change in 4.18 upgrade guide#23891
oscerd merged 1 commit into
apache:mainfrom
oscerd:CAMEL-23630-doc-sync-4.18-guide-to-main

Conversation

@oscerd

@oscerd oscerd commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Documentation sync: camel-dapr (CAMEL-23630) — 4.18 upgrade guide

Adds the camel-dapr upgrade note to camel-4x-upgrade-guide-4_18.adoc (under Upgrading from 4.18.1 to 4.18.3) on main.

Doc-sync follow-up to the 4.18.x backport (#23889) of #23886. Per the project's backport upgrade-guide policy, the version-specific upgrade guides on main are the canonical history across all release lines, so a change shipping in a 4.18.x patch must also be documented in the 4_18 guide on main — not only in the 4_21 guide (where #23886 already added it).

The note mirrors the 4_21 entry: the new DaprHeaderFilterStrategy / headerFilterStrategy option, and the removal of the producer-direction CamelDaprPubSubName / CamelDaprTopic headers from consumed dapr-pubsub exchanges.

The matching 4_14 guide entry (for the 4.14.x backport #23905) is in a separate follow-up: #23907 (this PR had already merged when the 4.14.x backport was prepared).


Prepared by Claude Code on behalf of Andrea Cosentino · 🤖 Generated with Claude Code

…de guide

The dapr-pubsub consumer header change (CAMEL-23630) was backported to
camel-4.18.x (apache#23889) and ships in 4.18.3. Per the backport upgrade-guide
policy, document it in camel-4x-upgrade-guide-4_18.adoc on main (the canonical
upgrade-guide history), mirroring the existing 4_21 entry.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@oscerd oscerd requested a review from davsclaus June 9, 2026 16:46
@github-actions

github-actions Bot commented Jun 9, 2026

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 Jun 9, 2026
@github-actions

github-actions Bot commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

🧪 CI tested the following changed modules:

  • docs

⚙️ View full build and test results

@gnodet gnodet left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Straightforward upgrade guide documentation for the camel-dapr header changes in 4.18.x. Correctly documents:

  • The addition of DaprHeaderFilterStrategy
  • The removal of CamelDaprPubSubName and CamelDaprTopic from consumer headers (now using Dapr metadata instead)

Documentation is clear and well-structured.

Fully automatic review from Claude Code

@oscerd oscerd merged commit d3072d9 into apache:main Jun 10, 2026
6 checks passed
@oscerd oscerd changed the title CAMEL-23630: Document camel-dapr 4.18.x consumer header change in 4.18 upgrade guide CAMEL-23630: Document camel-dapr backport consumer header change in 4.18 + 4.14 upgrade guides Jun 10, 2026
@oscerd oscerd changed the title CAMEL-23630: Document camel-dapr backport consumer header change in 4.18 + 4.14 upgrade guides CAMEL-23630: Document camel-dapr 4.18.x consumer header change in 4.18 upgrade guide Jun 10, 2026
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.

4 participants