fix(deps): bump the aws group across 1 directory with 9 updates

[dependabot]

Bumps the aws group with 6 updates in the / directory:

Package	From	To
aws-smithy-runtime-api	1.7.3	1.7.4
aws-types	1.3.3	1.3.5
aws-credential-types	1.2.1	1.2.2
aws-smithy-http	0.60.11	0.62.0
aws-smithy-json	0.60.7	0.61.1
aws-smithy-runtime	1.7.6	1.8.0

Updates aws-smithy-runtime-api from 1.7.3 to 1.7.4

Commits

• See full diff in compare view

Updates aws-smithy-types from 1.2.11 to 1.3.0

Commits

• See full diff in compare view

Updates aws-types from 1.3.3 to 1.3.5

Commits

• See full diff in compare view

Updates aws-credential-types from 1.2.1 to 1.2.2

Changelog

Sourced from aws-credential-types's changelog.

March 10th, 2025

New this release:

• (client, aws-sdk-rust#977, smithy-rs#1925, smithy-rs#3710) Updates the default HTTP client to be based on the 1.x version of hyper and updates the default TLS provider to rustls with aws-lc. For more information see the GitHub discussion.

March 4th, 2025

New this release:

• 🎉 (client, smithy-rs#121) Adds support for event stream operations with non-REST protocols such as RPC v2 CBOR.

February 20th, 2025

New this release:

• 🐛 (server) Fixed code generation failure that occurred when using Result as a shape name in Smithy models with constrained members by properly handling naming conflicts with Rust's built-in Result type
• 🐛 (server) Previously, models would fail to generate when both the list and at least one of its members was directly constrained with documentation comments

February 12th, 2025

February 3rd, 2025

January 28th, 2025

January 23rd, 2025

January 17th, 2025

January 14th, 2025

New this release:

• 🐛🎉 (client, smithy-rs#3845) S3 client behavior is updated to always calculate a checksum by default for operations that support it (such as PutObject or UploadPart), or require it (such as DeleteObjects). The default checksum algorithm is CRC32. Checksum behavior can be configured using when_supported and when_required options - in shared config using request_checksum_calculation, or as env variable using AWS_REQUEST_CHECKSUM_CALCULATION.

  The S3 client attempts to validate response checksums for all S3 API operations that support checksums. However, if the SDK has not implemented the specified checksum algorithm then this validation is skipped. Checksum validation behavior can be configured using when_supported and when_required options - in shared config using response_checksum_validation, or as env variable using AWS_RESPONSE_CHECKSUM_VALIDATION.

• 🐛🎉 (client, smithy-rs#3967) Updates client generation to conform with Smithy's updates to the httpChecksum trait.

• 🐛 (client, aws-sdk-rust#1234) Fix token bucket not being set for standard and adaptive retry modes

December 30th, 2024

December 26th, 2024

... (truncated)

Commits

• See full diff in compare view

Updates aws-smithy-async from 1.2.3 to 1.2.5

Commits

• See full diff in compare view

Updates aws-smithy-http from 0.60.11 to 0.62.0

Commits

• See full diff in compare view

Updates aws-smithy-json from 0.60.7 to 0.61.1

Commits

• See full diff in compare view

Updates aws-smithy-runtime from 1.7.6 to 1.8.0

Commits

• See full diff in compare view

Updates aws-smithy-eventstream from 0.60.5 to 0.60.8

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 16.86%. Comparing base (8a4afec) to head (aa7ae00).

Additional details and impacted files

@@             Coverage Diff             @@
##             main     #926       +/-   ##
===========================================
+ Coverage   13.83%   16.86%    +3.03%     
===========================================
  Files        2361      212     -2149     
  Lines      204802    20507   -184295     
  Branches   185166      871   -184295     
===========================================
- Hits        28329     3459    -24870     
+ Misses     174977    17048   -157929     
+ Partials     1496        0     -1496     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.