This is an automated email from the ASF dual-hosted git repository.
oscerd pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new a11ac9dee49a CAMEL-23577: docs - add "potential breaking change"
suffix to 9 header-rename sub-task entries in the 4.21 upgrade guide (#23505)
a11ac9dee49a is described below
commit a11ac9dee49a4f5b0d3080e353d22e2b33c385a8
Author: Andrea Cosentino <[email protected]>
AuthorDate: Tue May 26 09:34:41 2026 +0200
CAMEL-23577: docs - add "potential breaking change" suffix to 9
header-rename sub-task entries in the 4.21 upgrade guide (#23505)
Aligns nine CAMEL-23577 sub-task upgrade-guide entries with the convention
established for the camel-jira entry (and used for camel-grok,
camel-jgroups,
camel-dns, camel-milo): the heading is suffixed with `- potential breaking
change` to make it obvious to readers scanning the upgrade guide that the
section describes a header-value rename that may break routes that set the
header by its literal string value.
Headings updated:
- camel-web3j (CAMEL-23578, #23435)
- camel-openstack (CAMEL-23580, #23438)
- camel-pdf (CAMEL-23579, #23437)
- camel-elasticsearch / camel-opensearch (CAMEL-23581, #23442)
- camel-github2 (CAMEL-23582, #23454)
- camel-google-functions / camel-google-secret-manager /
camel-google-vision /
camel-google-text-to-speech / camel-google-speech-to-text (CAMEL-23583,
#23467)
- camel-arangodb (CAMEL-23585, #23469)
- camel-jt400 (CAMEL-23587, #23470)
- camel-mail (CAMEL-23591, #23478)
The camel-milo entry (CAMEL-23590, #23474) already shipped with the suffix
and is unchanged. No section content changes; only the 9 heading lines are
modified.
Tracker: CAMEL-23577
Reported by Claude Code on behalf of Andrea Cosentino
Signed-off-by: Andrea Cosentino <[email protected]>
---
.../ROOT/pages/camel-4x-upgrade-guide-4_21.adoc | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc
index 0d9af829173c..cdac43bbd6d6 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc
@@ -844,7 +844,7 @@ directions, aligning the component with the rest of the
Camel component catalog.
`Camel`-prefixed user-header names from Iggy messages can supply a custom
`headerFilterStrategy`
to restore the previous behaviour.
-=== camel-web3j
+=== camel-web3j - potential breaking change
The Exchange header constants in `Web3jConstants` have been renamed to follow
the
Camel naming convention used across the rest of the component catalog. The Java
@@ -955,7 +955,7 @@ A new accessor `web3jOperation()` is also generated for
`Web3jConstants.OPERATIO
(the producer dispatch header). This constant did not appear in the catalog
previously, so no DSL accessor renaming applies to it.
-=== camel-openstack
+=== camel-openstack - potential breaking change
The Exchange header constants in `OpenstackConstants`, `KeystoneConstants`,
`NovaConstants`, `CinderConstants`, `GlanceConstants`, `NeutronConstants`,
@@ -1095,7 +1095,7 @@ The generated Endpoint DSL header accessors on each
component's
`openstackOperation()`, `password()` -> `openstackKeystonePassword()`,
`adminPassword()` -> `openstackNovaAdminPassword()`, etc.).
-=== camel-pdf
+=== camel-pdf - potential breaking change
The Exchange header constants in `PdfHeaderConstants` have been renamed to
follow the Camel naming convention used across the rest of the component
@@ -1125,7 +1125,7 @@ As a consequence, the generated Endpoint DSL header
accessors on
* `decryptionMaterial()` -> `pdfDecryptionMaterial()`
* `filesToMerge()` -> `pdfFilesToMerge()`
-=== camel-elasticsearch / camel-opensearch
+=== camel-elasticsearch / camel-opensearch - potential breaking change
The Exchange header constants in `ElasticsearchConstants` and
`OpensearchConstants` have been renamed to follow the Camel naming convention
@@ -1182,7 +1182,7 @@ been renamed accordingly (`operation()` ->
`elasticsearchOperation()` /
`opensearchOperation()`, `indexId()` -> `elasticsearchIndexId()` /
`opensearchIndexId()`, etc.).
-=== camel-github2
+=== camel-github2 - potential breaking change
The producer-side Exchange header constants in `GitHub2Constants` have been
renamed to follow the Camel naming convention used across the rest of the
@@ -1219,7 +1219,7 @@ NOTE: The deprecated `camel-github` component (the
predecessor of
`camel-github2`) was removed in Camel 4.21 (see the _camel-github removal_
entry above), so the analogous rename does not apply there.
-=== camel-google-functions / camel-google-secret-manager / camel-google-vision
/ camel-google-text-to-speech / camel-google-speech-to-text
+=== camel-google-functions / camel-google-secret-manager / camel-google-vision
/ camel-google-text-to-speech / camel-google-speech-to-text - potential
breaking change
The Exchange header constants in these Google Cloud components carried a
`GoogleCloud<Service>` / `GoogleSecretManager` prefix that is not in the
@@ -1259,7 +1259,7 @@ The generated Endpoint DSL header accessor names are
unchanged (for example
deriving the accessor name; the accessors now return the new `Camel`-prefixed
values.
-=== camel-arangodb
+=== camel-arangodb - potential breaking change
Two Exchange header constants in `ArangoDbConstants` that were not in the
`Camel` namespace (and therefore not filtered by the default
@@ -1288,7 +1288,7 @@ As a consequence, the generated Endpoint DSL header
accessors on
`ArangoDbHeaderNameBuilder` have been renamed: `key()` -> `arangoDbKey()` and
`resultClassType()` -> `arangoDbResultClassType()`.
-=== camel-jt400
+=== camel-jt400 - potential breaking change
The two Exchange header constants in `Jt400Constants` that were not in the
`Camel` namespace (and therefore not filtered by the default
@@ -1318,7 +1318,7 @@ As a consequence, the generated Endpoint DSL header
accessors on
`Jt400HeaderNameBuilder` have been renamed: `kEY()` -> `jt400Key()` and
`senderInformation()` -> `jt400SenderInformation()`.
-=== camel-mail
+=== camel-mail - potential breaking change
The consumer-side dispatch header constants in `MailConstants` that control
post-processing of a consumed mail message used header values outside the
