CAMEL-23577: doc-sync 4.18.x/4.14.x header-rename upgrade-guide entries to main#23615
Merged
Merged
Conversation
Contributor
|
🌟 Thank you for your contribution to the Apache Camel project! 🌟 🐫 Apache Camel Committers, please review the following items:
|
Contributor
|
🧪 CI tested the following changed modules:
|
davsclaus
approved these changes
May 29, 2026
oscerd
force-pushed
the
docs/CAMEL-23577-guide-doc-sync
branch
from
aa1a03d to
41e850d
Compare
…es to main The camel-4x-upgrade-guide-4_XX.adoc files on main act as the canonical history across all release lines. The 2026-05 Exchange-header-constant rename cascade (CAMEL-23577) was backported to camel-4.18.x and camel-4.14.x with the corresponding upgrade-guide entries added on those maintenance branches, but the matching entries were never mirrored back into the canonical guides on main, leaving main's 4_18 / 4_14 guides out of sync with what actually shipped. This commit copies the missing sections verbatim from the maintenance branches into the matching guide files on main, inserted immediately after the existing camel-jira section so they group with the rest of the rename family. camel-4x-upgrade-guide-4_18.adoc (11 sections): pdf, arangodb, jt400, mail, github2, elasticsearch/opensearch, google-functions/secret-manager, openstack, shiro, web3j, milo camel-4x-upgrade-guide-4_14.adoc (9 sections): pdf, arangodb, jt400, mail, elasticsearch/opensearch, google-functions/secret-manager, openstack, shiro, web3j (github2 and milo are intentionally 4.18-only — those components do not exist on the 4.14.x branch.) Documentation only; no code changes. Tracker: CAMEL-23577 Signed-off-by: Andrea Cosentino <ancosen@gmail.com>
oscerd
force-pushed
the
docs/CAMEL-23577-guide-doc-sync
branch
from
41e850d to
7c01136
Compare
oscerd
added a commit
that referenced
this pull request
Jun 8, 2026
The camel-web3j entry in camel-4x-upgrade-guide-4_18.adoc was missing its opening table delimiter: the section jumped straight from the intro paragraph to the data rows, with only a closing |=== and no [options="header"] / |=== / header row. Asciidoctor reports "table missing leading separator; recovering automatically" and its table-recovery then cascades into the following tables (solr, cxf, dns) in the same file. This was latent on camel-4.18.x because the camel-website Antora validation only aggregates each repository's main branch, never the maintenance branches, so the broken table was never exercised. It surfaced when the 4_18 entries were doc-synced to main (apache/camel PR #23615), failing that PR's "PR doc validation" check. The equivalent table is well-formed on main (4_21 guide) and on camel-4.14.x; only this 4_18 copy lost its opening delimiter during the web3j 4.18.x backport. This commit restores the three missing lines so the table renders correctly. Documentation only; no code changes. Tracker: CAMEL-23577 Signed-off-by: Andrea Cosentino <ancosen@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Per the project's backport-upgrade-guide policy, the
camel-4x-upgrade-guide-4_XX.adocfiles onmainare the canonical history across all release lines. The 2026-05 Exchange-header-constant rename cascade (umbrella CAMEL-23577) was backported tocamel-4.18.xandcamel-4.14.x, and each backport added its upgrade-guide entry on the respective maintenance branch — but those entries were never mirrored back into the canonical guides onmain. As a resultmain's4_18/4_14guides were missing the rename family that actually shipped on the LTS branches.What this PR does
Copies the missing sections verbatim from the maintenance branches into the matching guide files on
main, inserted right after the existing=== camel-jirasection so they group with the rest of the rename family. Documentation only — no code changes.camel-4x-upgrade-guide-4_18.adoc— 11 sections added:pdf, arangodb, jt400, mail, github2, elasticsearch / opensearch, google-functions / google-secret-manager, openstack, shiro, web3j, milo
camel-4x-upgrade-guide-4_14.adoc— 8 sections added:pdf, arangodb, jt400, mail, openstack, shiro, web3j, google-functions / google-secret-manager
Notes:
github2andmiloare intentionally 4.18-only — those components do not exist on the 4.14.x branch.elasticsearch / opensearch4_14 entry was already present onmain(restored via CAMEL-23581: restore camel-elasticsearch / camel-opensearch section in 4_14 upgrade guide #23611), so it is not re-added here.Verification
== Upgrading from 4.18.1 to 4.18.3on 4_18; top/current section on 4_14), adjacent to the existingcamel-jirarename entry.Reviewers
@davsclaus @gnodet
🤖 Generated with Claude Code