July 16th, 2024

New this release:

• (client, smithy-rs#3742) Support stringArray type in endpoints params
• (client, smithy-rs#3755) Add support for operationContextParams Endpoints trait
• (client, smithy-rs#3591) aws_smithy_runtime_api::client::orchestrator::HttpRequest and aws_smithy_runtime_api::client::orchestrator::HttpResponse are now re-exported in generated clients so that using these types does not require directly depending on aws-smithy-runtime-api.

July 9th, 2024

Breaking Changes:

• ⚠️ (server, smithy-rs#3746) FromParts<Protocol>::Rejection must implement std::fmt::Display.

  Handlers can accept user-defined types if they implement
  FromParts with a Rejection
  type that implements std::fmt::Display (preferably std::error::Error) to enable error logging when parameter construction from request parts fails.

  See the changelog discussion for futher details.

New this release:

• (client, smithy-rs#3742) Support stringArray type in endpoints params
• 🐛 (client, smithy-rs#3744) Fix bug where stalled stream protection would panic with an underflow if the first event was logged too soon.

July 3rd, 2024

New this release:

• 🐛 (server, smithy-rs#3643) A feature, aws-lambda, has been added to generated SDKs to re-export types required for Lambda deployment.
• 🐛 (server, smithy-rs#3471, smithy-rs#3724, @djedward) Content-Type header validation now ignores parameter portion of media types.

Contributors
Thank you for your contributions! ❤

• @djedward (smithy-rs#3471, smithy-rs#3724)

June 19th, 2024

Breaking Changes:

• 🐛⚠️ (server, smithy-rs#3690) Fix request Content-Type header checking

  Two bugs related to how servers were checking the Content-Type header in incoming requests have been fixed:

  1. Content-Type header checking was incorrectly succeeding when no Content-Type header was present but one was expected.
  2. When a shape was @httpPayload-bound, Content-Type` header checking occurred even when no payload was being sent. In this case it is not necessary to check the header, since there is no content.

  This is a breaking change in that servers are now stricter at enforcing the expected Content-Type header is being sent by the client in general, and laxer when the shape is bound with @httpPayload.

June 17th, 2024

Internal and aws-sdk-rust-related changes only with this release

June 12th, 2024

Internal changes only with this release

June 10th, 2024

New this release:

• (all, smithy-rs#1925, smithy-rs#3673) Add support for v1 http_body::Body to aws_smithy_types::byte_stream::bytestream_util::PathBody.
• (all, smithy-rs#3637, @khuey) Add conversions from smithy StatusCode to http StatusCode.
• 🐛 (client, smithy-rs#3675, @DaStrom) Enable aws-smithy-runtime to compile in rustc 1.72.1

Contributors
Thank you for your contributions! ❤

• @DaStrom (smithy-rs#3675)
• @khuey (smithy-rs#3637)

June 3rd, 2024

New this release:

• (client, smithy-rs#3664) Reduce verbosity of various debug logs

May 28th, 2024

Internal changes only with this release

May 22nd, 2024

New this release:

• 🐛 (client, smithy-rs#3656, smithy-rs#3657) Fix the Content-Length enforcement so it is only applied to GET requests.