[dependabot]

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

Package	From	To
aws-credential-types	1.3.0	1.3.1
aws-types	1.6.0	1.7.0
aws-smithy-async	1.3.0	1.3.1
aws-smithy-http	0.64.0	0.64.2
aws-smithy-runtime	1.14.0	1.16.1
aws-smithy-runtime-api	1.16.0	1.19.2
aws-smithy-types	1.6.3	1.9.1
aws-smithy-http-client	1.4.0	1.5.2

Updates aws-credential-types from 1.3.0 to 1.3.1

Commits

• See full diff in compare view

Updates aws-types from 1.6.0 to 1.7.0

Changelog

Sourced from aws-types's changelog.

October 29th, 2026

Breaking Changes:

• ⚠️🎉 (server, smithy-rs#4894, smithy-rs#4906, @​fahadzub) Upgrade aws-smithy-http-server to 0.69.0 with schema-based serialization and multi-protocol routing for HTTP 1.x servers. Enable schema serde with codegen.schemaSerde: true and regenerate your server SDK. Review these migration changes when upgrading:

  • Protocol types such as RestJson1 now carry configuration. Replace unit-struct construction with RestJson1::default(). For request-specific serialization, use the protocol selected by routing so its configuration is preserved.
  • The HTTP 1.x server runtime uses Tower 0.5. Update application dependencies and middleware that use Tower utility types to Tower 0.5. aws-smithy-http-server-metrics and aws-smithy-http-server-metrics-macro 0.4.0 target server 0.69; upgrade the server and metrics crates together.
  • Schema serde calls IntoResponse<P>::into_response_with_protocol to frame errors using the selected protocol. Its default preserves the existing into_response conversion and the FromParts<P>::Rejection: IntoResponse<P> bound. Override the contextual method when an error needs protocol-specific framing. Generated-serde callers continue using into_response. Use response::ModeledRejection<E> for modeled extractor errors and the shared runtime_error::RuntimeError for framework errors.
  • AWS JSON routing uses the modeled operation name in both serde modes: getFoo uses X-Amz-Target: Service.getFoo. To also accept the former generated spelling Service.GetFoo, set capitalizeRoutes: true in the aws.protocols#awsJson1_0 or aws.protocols#awsJson1_1 section of customizationConfig.protocols.
  • Schema-serde RPC v2 CBOR streaming blob inputs use ByteStream instead of Blob. The CBOR document is collected and decoded before the handler is invoked; the stream contains the decoded blob bytes.

New this release:

• 🐛 (server, smithy-rs#2472, @​franco2002lu) Exclude @internal enum values from the enum value set in server constraint violation messages. Previously, rejecting an invalid enum value listed every value, including internal ones that should not be exposed to callers. Internal values are still accepted as valid input.
• (server, smithy-rs#4934, @​xz0803) Improve server routing performance for REST protocols. RestRouter now holds its RequestSpecs behind an Arc, so cloning the router shares each route's path regex and its match cache instead of rebuilding the cache: on every request for aws_smithy_http_server::serve, and on every connection for aws-smithy-legacy-http-server.
• 🐛 (client, smithy-rs#4967) Generated endpoint rule-set tests no longer run the validators in ParamsBuilder::build(), so a test case with an invalid Region reaches the rules instead of panicking with invalid params. Requests still run the validators.
• 🐛 (server, @​fahadzub) Encode shared runtime validation messages and initial request frame rejection messages as CBOR maps for rpcv2Cbor, so clients can decode the message. Modeled validation errors, including custom validation types, retain their own schema and serialized fields.

Contributors Thank you for your contributions! ❤

• @​fahadzub (smithy-rs#4894, smithy-rs#4906)
• @​franco2002lu (smithy-rs#2472)
• @​xz0803 (smithy-rs#4934)

October 27th, 2026

... (truncated)

Commits

• See full diff in compare view

Updates aws-smithy-async from 1.3.0 to 1.3.1

Commits

• See full diff in compare view

Updates aws-smithy-http from 0.64.0 to 0.64.2

Commits

• See full diff in compare view

Updates aws-smithy-runtime from 1.14.0 to 1.16.1

Changelog

Sourced from aws-smithy-runtime's changelog.

October 29th, 2026

Breaking Changes:

• ⚠️🎉 (server, smithy-rs#4894, smithy-rs#4906, @​fahadzub) Upgrade aws-smithy-http-server to 0.69.0 with schema-based serialization and multi-protocol routing for HTTP 1.x servers. Enable schema serde with codegen.schemaSerde: true and regenerate your server SDK. Review these migration changes when upgrading:

  • Protocol types such as RestJson1 now carry configuration. Replace unit-struct construction with RestJson1::default(). For request-specific serialization, use the protocol selected by routing so its configuration is preserved.
  • The HTTP 1.x server runtime uses Tower 0.5. Update application dependencies and middleware that use Tower utility types to Tower 0.5. aws-smithy-http-server-metrics and aws-smithy-http-server-metrics-macro 0.4.0 target server 0.69; upgrade the server and metrics crates together.
  • Schema serde calls IntoResponse<P>::into_response_with_protocol to frame errors using the selected protocol. Its default preserves the existing into_response conversion and the FromParts<P>::Rejection: IntoResponse<P> bound. Override the contextual method when an error needs protocol-specific framing. Generated-serde callers continue using into_response. Use response::ModeledRejection<E> for modeled extractor errors and the shared runtime_error::RuntimeError for framework errors.
  • AWS JSON routing uses the modeled operation name in both serde modes: getFoo uses X-Amz-Target: Service.getFoo. To also accept the former generated spelling Service.GetFoo, set capitalizeRoutes: true in the aws.protocols#awsJson1_0 or aws.protocols#awsJson1_1 section of customizationConfig.protocols.
  • Schema-serde RPC v2 CBOR streaming blob inputs use ByteStream instead of Blob. The CBOR document is collected and decoded before the handler is invoked; the stream contains the decoded blob bytes.

New this release:

• 🐛 (server, smithy-rs#2472, @​franco2002lu) Exclude @internal enum values from the enum value set in server constraint violation messages. Previously, rejecting an invalid enum value listed every value, including internal ones that should not be exposed to callers. Internal values are still accepted as valid input.
• (server, smithy-rs#4934, @​xz0803) Improve server routing performance for REST protocols. RestRouter now holds its RequestSpecs behind an Arc, so cloning the router shares each route's path regex and its match cache instead of rebuilding the cache: on every request for aws_smithy_http_server::serve, and on every connection for aws-smithy-legacy-http-server.
• 🐛 (client, smithy-rs#4967) Generated endpoint rule-set tests no longer run the validators in ParamsBuilder::build(), so a test case with an invalid Region reaches the rules instead of panicking with invalid params. Requests still run the validators.
• 🐛 (server, @​fahadzub) Encode shared runtime validation messages and initial request frame rejection messages as CBOR maps for rpcv2Cbor, so clients can decode the message. Modeled validation errors, including custom validation types, retain their own schema and serialized fields.

Contributors Thank you for your contributions! ❤

• @​fahadzub (smithy-rs#4894, smithy-rs#4906)
• @​franco2002lu (smithy-rs#2472)
• @​xz0803 (smithy-rs#4934)

October 27th, 2026

... (truncated)

Commits

• See full diff in compare view

Updates aws-smithy-runtime-api from 1.16.0 to 1.19.2

Commits

• See full diff in compare view

Updates aws-smithy-types from 1.6.3 to 1.9.1

Commits

• See full diff in compare view

Updates aws-smithy-http-client from 1.4.0 to 1.5.2

Commits

• See full diff in compare view

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-29T17:11:31.952484Z	58e883c	New commits

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[datadoghq-integration]

AWS-enabled builds cannot compile because aws-config 1.12.0 passes a schema 0.2.0 protocol type into aws-types 1.7.0, which expects schema 1.1.0.

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit 34ec5ad}

[datadoghq-integration]

Keep aws-types compatible with the pinned aws-config

Enabling aws-core compiles the unchanged aws-config 1.12.0, which unconditionally calls builder.set_protocol(self.protocol) with SharedClientProtocol from aws-smithy-schema 0.2.0. Upgraded aws-types 1.7.0 expects the corresponding type from schema 1.1.0. These are distinct Rust types, so AWS-enabled builds fail even without a custom protocol configured. Regenerate the lockfile with a compatible aws-config/aws-types pair, either upgrading them together or retaining the compatible aws-types version.

React: 👍 useful · 👎 wrong · 😕 unclear · 👀 right, but not acting on it

What each reaction means

• 👍 Useful: correct, and you're fixing it or will.
• 👎 Wrong: the finding is incorrect, for example the bug can't happen or the code was misread.
• 😕 Unclear: you can't tell what it means or why it matters.
• 👀 Right, not acting: correct, but intended, out of scope for this PR, a known risk, or too minor.

_{🤖 Bits Code Review · Open Bits AI session}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: adec084993

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Keep the AWS crates on one compatibility line

When any AWS-backed source, sink, or secrets provider is enabled, this upgrades the Smithy runtime to the new compatibility line while leaving aws-config at 1.12.0 and every service client on the previous line; the resulting lockfile contains both aws-smithy-schema 0.2.0 and 1.1.0. AWS's October 20 release notes explicitly state that these affected crates must be upgraded together and that a partial update with a previously published aws-config is unsupported. Upgrade aws-config and the service SDK crates as part of this change, or keep the runtime crates on their previous versions.

Useful? React with 👍 / 👎.