Skip to content

CAMEL-23575: docs - sync camel-mongodb-gridfs 4.14 upgrade-guide entry to main#23487

Open
oscerd wants to merge 1 commit into
apache:mainfrom
oscerd:doc-sync/CAMEL-23575-4.14-guide-to-main
Open

CAMEL-23575: docs - sync camel-mongodb-gridfs 4.14 upgrade-guide entry to main#23487
oscerd wants to merge 1 commit into
apache:mainfrom
oscerd:doc-sync/CAMEL-23575-4.14-guide-to-main

Conversation

@oscerd
Copy link
Copy Markdown
Contributor

@oscerd oscerd commented May 24, 2026

Summary

Doc-sync companion to the #23413 / CAMEL-23575 backport to camel-4.14.x (#23486).

Per the backport upgrade-guide policy in CLAUDE.md, the version-specific camel-4x-upgrade-guide-4_XX.adoc files for all release lines live on main as the canonical history. The code fix for CAMEL-23575 is backported to the camel-4.14.x maintenance branch (4.14.8), so the matching upgrade-guide entry must also be present in camel-4x-upgrade-guide-4_14.adoc on main — otherwise main's 4.14 guide drifts out of sync with what ships on 4.14.x.

This PR adds the === camel-mongodb-gridfs - potential breaking change note to the "Upgrading from 4.14.3 to 4.14.8" section, documenting:

  • the gridfs.* -> CamelGridFs* header constant value renames, and
  • the cascading GridFsHeaderNameBuilder Endpoint DSL accessor renames.

Routes referencing the constants symbolically are unaffected; only routes using the literal string keys or the fluent builder methods need updating.

The "- potential breaking change" heading suffix is added for consistency with the neighbouring camel-jira / camel-cxf / camel-jgroups entries in the same release section (CAMEL-23577 sweep convention).

Related

Docs-only change — no build required.

Prepared by Claude Code on behalf of Andrea Cosentino.

…y to main

Adds the camel-mongodb-gridfs header-constant rename note to the
"Upgrading from 4.14.3 to 4.14.8" section of camel-4x-upgrade-guide-4_14.adoc
on main, matching the backport to camel-4.14.x (apache#23486, cherry-pick of
apache#23413 / CAMEL-23575). Marked "- potential breaking change" for
consistency with the neighbouring camel-jira / camel-cxf / camel-jgroups
entries in the same release section (CAMEL-23577 sweep convention).

Per the backport upgrade-guide policy, the version-specific upgrade-guide
files for all releases live on main as the canonical history; the entry
for the 4.14.8 release line must therefore be present here even though
the code fix is backported to the camel-4.14.x maintenance branch.

Reported by Claude Code on behalf of Andrea Cosentino.

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

@gnodet gnodet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Docs-only change — adds the camel-mongodb-gridfs header-rename upgrade note to the 4.14 guide on main, completing the doc-sync for the backport chain (#23413#23473#23486).

What I checked:

  • Placement: Correctly inserted in the "Upgrading from 4.14.3 to 4.14.8" section, after the existing camel-jira entry.
  • Content: All 5 header constant renames and all 5 Endpoint DSL accessor renames documented accurately, matching the code changes in #23486.
  • Policy: Follows the backport upgrade-guide policy — entry lives on main as the canonical history across release lines.
  • Heading convention: Uses "- potential breaking change" suffix, consistent with neighbouring entries in the same section.

LGTM.

Claude Code on behalf of Guillaume Nodet

@github-actions
Copy link
Copy Markdown
Contributor

🧪 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.

4 participants