(camel) branch main updated: CAMEL-23132: Document ListObjectsV2 migration in upgrade guide

[fm...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

Croway 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 07e409a8b720 CAMEL-23132: Document ListObjectsV2 migration in upgrade guide
07e409a8b720 is described below

commit 07e409a8b720d523e15fe1fdc20a0596593c2773
Author: Croway <fe...@gmail.com>
AuthorDate: Wed May 13 13:02:31 2026 +0200

    CAMEL-23132: Document ListObjectsV2 migration in upgrade guide
---
 .../modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc        | 10 ++++++++++
 1 file changed, 10 insertions(+)

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 d3b12a318ea0..ccfecdbcc9aa 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
@@ -307,6 +307,16 @@ previous code path silently produced `null` whenever a route mixed `converse` an
 calls. If you were not setting the guardrail identifier via header, the endpoint-level
 `guardrailIdentifier` option continues to work without changes.
 
+=== camel-aws2-s3
+
+The `listObjects` operation now uses the `ListObjectsV2` AWS API instead of the deprecated `ListObjects` API.
+If you use `pojoRequest=true` with `operation=listObjects`, you must change your request and response types:
+
+* `ListObjectsRequest` -> `ListObjectsV2Request`
+* `ListObjectsResponse` -> `ListObjectsV2Response`
+
+The non-POJO path (header-based configuration) is updated automatically and requires no changes.
+
 === camel-nats
 
 Fixed the JetStream consumer pull subscription mode (which is the default) so that messages are