Skip to content

chore(docs): sync 4.18 and 4.14 upgrade guides with backported entries#22969

Open
oscerd wants to merge 1 commit intoapache:mainfrom
oscerd:ci-fix/sync-upgrade-guides-4_18-4_14
Open

chore(docs): sync 4.18 and 4.14 upgrade guides with backported entries#22969
oscerd wants to merge 1 commit intoapache:mainfrom
oscerd:ci-fix/sync-upgrade-guides-4_18-4_14

Conversation

@oscerd
Copy link
Copy Markdown
Contributor

@oscerd oscerd commented May 5, 2026

Summary

The 4.18 and 4.14 upgrade guides on `main` had drifted out of sync with their counterparts on the maintenance branches. Backport PRs for CAMEL-23373 (camel-jms) and CAMEL-23414 (camel-hazelcast) updated only the maintenance branches; the entries never made it back to `main`'s copies.

This PR adds the missing entries so the canonical upgrade guides on `main` reflect what actually shipped (or is shipping) in 4.18.3 and 4.14.8.

Changes

`camel-4x-upgrade-guide-4_18.adoc` (under "Upgrading from 4.18.1 to 4.18.3")

`camel-4x-upgrade-guide-4_14.adoc` (under section for 4.14.8)

Not included

Test plan

Documentation-only change. No build verification needed beyond the AsciiDoc preview.


Claude Code on behalf of Andrea Cosentino

The camel-4x-upgrade-guide-4_18.adoc and camel-4x-upgrade-guide-4_14.adoc
files on main had drifted out of sync with their counterparts on the
camel-4.18.x and camel-4.14.x branches: backport PRs for CAMEL-23373
(camel-jms - Disable ObjectMessage by default) and CAMEL-23414
(camel-hazelcast - Allow customization of SerializationConfig on managed
Hazelcast instances) updated only the maintenance branches.

Add the missing camel-jms and camel-hazelcast entries to both guides on
main, mirroring the prose already present on the 4.18.x and 4.14.x
branches. Existing camel-core entries are preserved. Section titles on
main are kept as-is; only fixed the typo "4.18.8" -> "4.14.8" in the
4.14 guide.

camel-sjms / camel-sjms2 (CAMEL-23409) is intentionally not included
yet: the 4.18.x backport (apache#22968) is still open, and this PR will be
followed up once that lands.

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

github-actions Bot commented May 5, 2026

🌟 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
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 5, 2026

🧪 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