Skip to content

CAMEL-23522: doc-sync 4.18 upgrade guide for camel-mail mail.smtp.* gating#23383

Merged
oscerd merged 1 commit into
apache:mainfrom
oscerd:doc-sync/CAMEL-23522-4.18-guide-to-main
May 21, 2026
Merged

CAMEL-23522: doc-sync 4.18 upgrade guide for camel-mail mail.smtp.* gating#23383
oscerd merged 1 commit into
apache:mainfrom
oscerd:doc-sync/CAMEL-23522-4.18-guide-to-main

Conversation

@oscerd
Copy link
Copy Markdown
Contributor

@oscerd oscerd commented May 20, 2026

Summary

Doc-sync of the camel-mail mail.smtp.* / mail.smtps.* gating entry from camel-4.18.x onto main's copy of camel-4x-upgrade-guide-4_18.adoc, per the project's backport upgrade-guide policy in CLAUDE.md:

The camel-4x-upgrade-guide-4_XX.adoc files for ALL versions live on main and act as the canonical history across all releases. When a PR is backported to a maintenance branch and adds an upgrade-guide note for that release line, the corresponding entry must ALSO be added to the matching camel-4x-upgrade-guide-4_XX.adoc file on main.

This PR mirrors the entry added in #23381 (backport to camel-4.18.x) onto main, immediately after the existing camel-neo4j entry in the "Upgrading from 4.18.1 to 4.18.3" section.

Linked

Test plan

  • Single docs file added; no code changes.
  • Identical wording to the same section on the camel-4.18.x branch.

Claude Code on behalf of Andrea Cosentino

…ating

Mirror the 4.18.x upgrade-guide entry for CAMEL-23522 (camel-mail - gate JavaMail session
properties from headers behind opt-in) onto main, per the project's backport upgrade-guide
policy: the camel-4x-upgrade-guide-4_XX.adoc files on main act as the canonical history
across all releases, so any entry added on a maintenance branch must also land here.

Companion to the backport PR against camel-4.18.x (apache#23381) and the main PR (apache#23362).

Signed-off-by: Andrea Cosentino <ancosen@gmail.com>
@oscerd oscerd requested review from davsclaus and gnodet May 20, 2026 16:24
@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 20, 2026
@github-actions
Copy link
Copy Markdown
Contributor

🧪 CI tested the following changed modules:

  • docs

⚙️ View full build and test results

@oscerd oscerd merged commit 984e8d2 into apache:main May 21, 2026
7 checks passed
oscerd added a commit that referenced this pull request May 21, 2026
…ating (#23418)

Mirror the 4.14.x upgrade-guide entry for CAMEL-23522 (camel-mail - gate JavaMail session
properties from headers behind opt-in) onto main, per the project's backport upgrade-guide
policy: the camel-4x-upgrade-guide-4_XX.adoc files on main act as the canonical history
across all releases, so any entry added on a maintenance branch must also land here.

Companion to the backport PR against camel-4.14.x (#23416), the 4.18.x backport (#23381), the
4.18 doc-sync (#23383) and the main PR (#23362).

Signed-off-by: Andrea Cosentino <ancosen@gmail.com>
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.

3 participants