Skip to content

Latest commit

 

History

History
57 lines (45 loc) · 2.41 KB

CHANGELOG.md

File metadata and controls

57 lines (45 loc) · 2.41 KB

Change Log

Unreleased

v0.6.0

Breaking Changes

  • Generated operation outputs and modeled errors now reserve a response_metadata attribute, carrying the request ID, extended request ID, and HTTP status code of the response that produced them. A modeled member named responseMetadata on an output or error is now generated as response_metadata_ to avoid the collision; only the Python attribute name changes, not the wire representation.

v0.5.0

Breaking Changes

  • Removed the deprecated unprefixed aliases for generated AWS service clients. Imports such as BedrockRuntimeClient must now use the Async-prefixed name, such as AsyncBedrockRuntimeClient.
  • Changed all generated AWS clients to use AIOHTTPClient as their default transport, including services configured for HTTP/2 or event streaming. Applications that require the CRT transport, such as those using bidirectional event streams, must install the generated client's awscrt extra and explicitly configure AWSCRTHTTPClient.
  • Removed the legacy Config class from generated AWS clients in favor of the service-specific, async-resolved Async<SdkId>Config class, such as AsyncBedrockRuntimeConfig. Explicit configuration must now be resolved with await Async<SdkId>Config.resolve(...) before it is passed to the client.

v0.4.0

Breaking Changes

  • Renamed generated AWS service clients to include Async (e.g. BedrockRuntimeClient is now AsyncBedrockRuntimeClient) to match the Python community convention for async clients. For clients that were already published under the unprefixed name, the old name remains available as a deprecated alias that emits a DeprecationWarning and will be removed in an upcoming release. The unprefixed name will later be reintroduced for synchronous clients.