Skip to content

[chore](thirdparty) Upgrade aws-sdk-cpp from 1.11.219 to 1.11.221 - #66851

Open
Owen-CH-Leung wants to merge 1 commit into
apache:masterfrom
qube-rt:bump-aws-sdk-pin-only
Open

[chore](thirdparty) Upgrade aws-sdk-cpp from 1.11.219 to 1.11.221#66851
Owen-CH-Leung wants to merge 1 commit into
apache:masterfrom
qube-rt:bump-aws-sdk-pin-only

Conversation

@Owen-CH-Leung

@Owen-CH-Leung Owen-CH-Leung commented Aug 17, 2026

Copy link
Copy Markdown

What problem does this PR solve?

Related PR: #66555

Problem Summary:

Bumps the pinned aws-sdk-cpp from 1.11.219 to 1.11.221 in thirdparty/vars.sh. No source changes.

1.11.221 is the first release that ships GeneralHTTPCredentialsProvider.h, which is the prerequisite for solving #66554. This PR is deliberately pin-only so that the pre-built thirdparty artifacts and the docker image are re-published against 1.11.221 before any code depends on the new header. #66555 is the follow-up PR that uses it.

Release note

None

Check List (For Author)

  • Test

    • Regression test
    • Unit Test
    • Manual test (add detailed scripts or steps below)
    • No need to test or manual test. Explain why:
      • This is a refactor/code format and no logic has been changed.
      • Previous test can cover this change.
      • No code files have been changed.
      • Other reason
  • Behavior changed:

    • No.
    • Yes.
  • Does this need documentation?

    • No.
    • Yes.

Check List (For Reviewer who merge this PR)

  • Confirm the release note
  • Confirm test cases
  • Confirm document
  • Add branch pick label

@hello-stephen

Copy link
Copy Markdown
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@Owen-CH-Leung

Copy link
Copy Markdown
Author

run buildall

@Owen-CH-Leung

Copy link
Copy Markdown
Author

@morningman @sollhui

Can I ask for your review for this PR ? Thanks a lot

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