Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update aws-sdk-s3 1.146.1 → 1.156.0 (minor) #1326

Closed
wants to merge 1 commit into from

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Jul 3, 2024

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ aws-sdk-s3 (1.146.1 → 1.156.0) · Repo · Changelog

Release Notes

Too many releases to show here. View the full release notes.

↗️ aws-partitions (indirect, 1.948.0 → 1.953.0) · Repo

Sorry, we couldn't find anything useful about this release.

↗️ aws-sdk-core (indirect, 3.199.0 → 3.201.1) · Repo · Changelog

Release Notes

3.201.1 (from changelog)

  • Issue - Fix Aws::ProcessCredentials warning in cases where shared config is used.

3.201.0 (from changelog)

  • Feature - Updated Aws::STS::Client with the latest API changes.

  • Feature - Updated Aws::SSOOIDC::Client with the latest API changes.

  • Feature - Updated Aws::SSO::Client with the latest API changes.

  • Feature - Support auth trait to enable SigV4a based services.

  • Feature - Support configuration for sigv4a signing regions using ENV['AWS_SIGV4A_SIGNING_REGION_SET'], sigv4a_signing_region_set shared config, or the sigv4a_signing_region_set client option.

3.200.0 (from changelog)

  • Feature - Updated Aws::STS::Client with the latest API changes.

  • Feature - Updated Aws::SSOOIDC::Client with the latest API changes.

  • Feature - Updated Aws::SSO::Client with the latest API changes.

Does any of this look wrong? Please let us know.

↗️ aws-sdk-kms (indirect, 1.87.0 → 1.88.0) · Repo · Changelog

Release Notes

1.88.0 (from changelog)

  • Feature - Code Generated Changes, see ./build_tools or aws-sdk-core's CHANGELOG.md for details.

Does any of this look wrong? Please let us know.


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot added the depfu label Jul 3, 2024
@mitlib mitlib temporarily deployed to thesis-submit-pr-1326 July 3, 2024 21:19 Inactive
@coveralls
Copy link

Coverage Status

coverage: 98.313%. remained the same
when pulling 350f8b2 on depfu/update/aws-sdk-s3-1.156.0
into 2301b7e on main.

@depfu depfu bot force-pushed the depfu/update/aws-sdk-s3-1.156.0 branch from 350f8b2 to 389b743 Compare July 8, 2024 20:21
@depfu depfu bot changed the title Update aws-sdk-s3 1.154.0 → 1.156.0 (minor) Update aws-sdk-s3 1.146.1 → 1.156.0 (minor) Jul 8, 2024
@coveralls
Copy link

Coverage Status

coverage: 98.313%. remained the same
when pulling 389b743 on depfu/update/aws-sdk-s3-1.156.0
into 6f04a8e on main.

Copy link
Contributor Author

depfu bot commented Jul 10, 2024

Closing because this update has already been applied

@depfu depfu bot closed this Jul 10, 2024
@depfu depfu bot deleted the depfu/update/aws-sdk-s3-1.156.0 branch July 10, 2024 12:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants