Backport of Update AWS SDK versions to the latest into v1.8 #34805
Conversation
This file contains 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
gdavison
approved these changes
Mar 8, 2024
radditude
force-pushed
the
backport/update_deps/mentally-integral-wasp
branch
from
1ee6dbc
to
b26ec33
Compare
|
Reminder for the merging maintainer: if this is a user-visible change, please update the changelog on the appropriate release branch. |
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Backport
This PR is auto-generated from #34796 to be assessed for backporting due to the inclusion of the label 1.8-backport.
The below text is copied from the body of the original PR.
This pull request updates the AWS SDKs to the latest version.
The intent is to fix #34528, which is intermittent and can't be easily reproduced.
The root cause was discussed in the relevant AWS SDK issue and AWS folks couldn't reproduce this situation on the latest versions of their SDK.
Hence, this pull request.
Target Release
1.7.x, 1.8.x
Draft CHANGELOG entry
BUG FIXES
Overview of commits