Skip to content

CAMEL-25645: camel-milo - upgrade guide notes for 4.22.3 and 4.18.6 - #28055

Merged
davsclaus merged 1 commit into
apache:mainfrom
oscerd:docs/CAMEL-25645-upgrade-guide-4.22.3-4.18.6
Oct 19, 2026
Merged

davsclaus merged 1 commit into
apache:mainfrom
oscerd:docs/CAMEL-25645-upgrade-guide-4.22.3-4.18.6

Conversation

@oscerd

@oscerd oscerd commented Oct 18, 2026 •

Copy link
Copy Markdown
Contributor

Summary

CAMEL-25645

Upgrade guide notes for the backports of #27824, which are merged:

The text is the same as the 4.24 note added by #27824, since the behaviour is the same on these branches. Documentation only. Rebased onto main after #28052, keeping a single 4.22.3 heading.

Claude Code on behalf of Andrea Cosentino

🤖 Generated with Claude Code

@oscerd
oscerd requested review from davsclaus and gnodet October 18, 2026 11:00
@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 Oct 18, 2026
@github-actions

github-actions Bot commented Oct 18, 2026 •

Copy link
Copy Markdown
Contributor

🧪 CI tested the following changed modules:

  • docs

🔬 Scalpel shadow comparison — Scalpel: 0 of 706 tested, 0 compile-only — current: 0 all tested

Maveniverse Scalpel detected 0 affected modules (current approach: 0).

Skip-tests mode would test 0 modules (1 direct + 0 downstream), skip tests for 0 (generated code, meta-modules)

Modules Scalpel would test (0)

ℹ️ Shadow mode — Scalpel observes but does not affect test execution. Learn more


⚙️ View full build and test results

@davsclaus davsclaus 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.

Thanks @oscerd. I checked the note against the backports. Both copies match the 4.24 entry word for word. The trust-list, certificateValidator and trustAllCertificates behaviour, and the log and exception messages it quotes, are the same in #28053 (camel-4.22.x) and #28054 (camel-4.18.x). The differences from main are only branch context: the cache id, the security = "insecure:ssl" attribute that @UriParam lacks on 4.18.x, and the main-only SecurityUtils owner map. None of them changes what the note describes.

The placement is right. The fix is not in the camel-4.22.2 tag, so it goes in a new "Upgrading from 4.22.2 to 4.22.3" section, and on 4.18 it sits in the 4.18.6 section. The AsciiDoc follows the surrounding headings. The earlier camel-milo - potential breaking change entry in the 4.18 guide is about the CamelMiloAwait header, so nothing is duplicated.

Two merge-order points, neither blocking:

  • Merge this after #28053 and #28054, so the guide does not announce a change for a release that misses it.
  • #28052 adds the same 4.22.3 heading at the same place (details inline).

Claude Code on behalf of Claus Ibsen

@davsclaus

Copy link
Copy Markdown
Contributor

@oscerd #28052 is merged, so this now conflicts on the == Upgrading from 4.22.2 to 4.22.3 heading in camel-4x-upgrade-guide-4_22.adoc (see the inline comment). Could you rebase and keep one 4.22.3 heading with the milo note and the elasticsearch/opensearch notes under it? The backports #28053 and #28054 are merged, so it can go in right after.

Claude Code on behalf of Claus Ibsen

The OPC UA client validates the server certificate on the camel-4.22.x and
camel-4.18.x branches too. The 4.22.2 release was already cut when the
change was backported, so its note goes into the section for 4.22.3.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Andrea Cosentino <ancosen@gmail.com>
@oscerd
oscerd force-pushed the docs/CAMEL-25645-upgrade-guide-4.22.3-4.18.6 branch from 1c275b1 to 8332b5d Compare October 19, 2026 07:14

@davsclaus davsclaus 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.

The rebase fixes the heading conflict: there is now a single == Upgrading from 4.22.2 to 4.22.3 with the milo note first and the elasticsearch/opensearch notes from #28052 unchanged, and the 4.18 note sits inside Upgrading from 4.18.5 to 4.18.6. The text matches the 4.24 note from #27824, and the options and log messages it names (trustListDirectory, certificateValidator, trustAllCertificates, the two WARN messages) exist on camel-4.22.x and camel-4.18.x after #28053/#28054. Merges cleanly with main and with #28078 in either order.

Claude Code on behalf of Claus Ibsen. This review was generated by an AI agent and may contain inaccuracies. Please verify all suggestions before applying.

@davsclaus davsclaus added this to the 4.24.0 milestone Oct 19, 2026
@davsclaus
davsclaus merged commit aff5697 into apache:main Oct 19, 2026
7 checks passed
@oscerd
oscerd deleted the docs/CAMEL-25645-upgrade-guide-4.22.3-4.18.6 branch October 19, 2026 16:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants