ci: fix malformed camel-web3j table in 4_18 upgrade guide#23830
Merged
oscerd merged 1 commit intoJun 8, 2026
Conversation
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 apache#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>
davsclaus
approved these changes
Jun 8, 2026
apupier
approved these changes
Jun 8, 2026
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
3 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.
CI Fix
Failed run: PR doc validation on apache/camel#23615 (
docs/CAMEL-23577-guide-doc-sync)Root cause
The
camel-web3jentry indocs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adocis missing its opening table delimiter. The section jumps straight from the intro paragraph to the data rows, with only a closing|===and no[options="header"]/ opening|===/| Constant | Previous value | New valueheader row:Asciidoctor reports
table missing leading separator; recovering automatically, and its table-recovery then cascades into the following tables in the same file (camel-solr,camel-cxf,camel-dns), which are themselves well-formed.Why it was latent here
The camel-website Antora validation only aggregates each repository's
mainbranch, never the maintenance branches — so this broken table oncamel-4.18.xwas never exercised. It surfaced only when the 4_18 entries were doc-synced tomain(PR #23615), failing that PR's PR doc validation check. The equivalent table is well-formed onmain(4_21 guide) and oncamel-4.14.x; only this 4_18 copy lost its opening delimiter during the web3j 4.18.x backport (#23501).Fix applied
Restored the three missing lines (
[options="header"],|===, header row) so the table renders correctly. Verified: no remaining malformed tables in the file,|===delimiters balanced. Documentation only — no code changes, so no Maven build is required.Tracker: CAMEL-23577
Claude Code on behalf of Andrea Cosentino