Skip to content

pin aws-sdk to 2.29.52#39

Merged
AbdelHedhili merged 2 commits intomainfrom
aws_sdk_2.29
Apr 3, 2026
Merged

pin aws-sdk to 2.29.52#39
AbdelHedhili merged 2 commits intomainfrom
aws_sdk_2.29

Conversation

@AbdelHedhili
Copy link
Copy Markdown
Contributor

@AbdelHedhili AbdelHedhili commented Apr 3, 2026

PR Summary

Pin the sdk version to fix the incompatibility since spring-cloud-aws 3.3 to 3.4 upgrade.

Using RequestChecksumCalculation.WHEN_REQUIRED fixed the issue except for the delete requests that caused an md5-content missing so we pin the version for now instead.

see aws/aws-sdk-java-v2#5805 and aws/aws-sdk-java-v2#5802

Signed-off-by: Abdelsalem <abdelsalem.hedhili@rte-france.com>
@AbdelHedhili AbdelHedhili self-assigned this Apr 3, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 3, 2026

Warning

Rate limit exceeded

@AbdelHedhili has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 8 minutes and 34 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 8 minutes and 34 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: dd124d32-5ec1-4d8b-9f3b-3283a685b95f

📥 Commits

Reviewing files that changed from the base of the PR and between ec23f1d and f0a3590.

📒 Files selected for processing (1)
  • pom.xml
📝 Walkthrough

Walkthrough

Maven build configuration is updated to upgrade spring-cloud-aws from version 3.4.0 to 3.4.2. A new AWS SDK version property is introduced (2.29.52) and an explicit software.amazon.awssdk:s3 dependency is added with pinned version to override transitive dependencies.

Changes

Cohort / File(s) Summary
Maven Configuration
pom.xml
Updated spring-cloud-aws version from 3.4.0 to 3.4.2; added aws-sdk.version property set to 2.29.52; added explicit software.amazon.awssdk:s3 dependency with pinned version to manage AWS SDK module during upgrade.
🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title 'pin aws-sdk to 2.29.52' directly and concisely describes the main change—pinning a specific AWS SDK version—matching the primary objective of the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description check ✅ Passed The pull request description clearly explains the purpose of pinning the AWS SDK version to fix an incompatibility from the spring-cloud-aws 3.3 to 3.4 upgrade, with relevant issue references.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Signed-off-by: Abdelsalem <abdelsalem.hedhili@rte-france.com>
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented Apr 3, 2026

@AbdelHedhili AbdelHedhili requested a review from jonenst April 3, 2026 09:24
@AbdelHedhili AbdelHedhili merged commit a3cf62d into main Apr 3, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants