Update smithy-rs servers' dependencies on `http`, `http-body`, `hyper`, and `tower-http`.

[david-perez]

Generated server SDKs use:

[dependencies.http]
version = "0.2.9"
[dev-dependencies.hyper]
version = "0.14.12"

And aws-smithy-http-server uses:

http = "0.2"
http-body = "0.4"
hyper = { version = "0.14.26", features = ["server", "http1", "http2", "tcp", "stream"] }
tower-http = { version = "0.3", features = ["add-extension", "map-response-body"] }

This is a breaking change because types from these crates are exposed in the tower::Service the generated SDKs export. http, http-body, hyper crates went 1.x.

Middleware authors using the 0.x versions of the http and http-body will be affected.

[djc]

Is this a duplicate of #1925?

[david-perez]

#1925 tracks the upgrade for smithy-rs clients, this issue is for servers.

[david-perez]

I think the only overlap of types depending on these crates used by both client and server is that servers (unfortunately) use SdkBody, but SdkBody has a from_body_1_x, so we could give this a go server-side.

It'd be better if the upgrade in both server and client went out in the same smithy-rs release though, to minimize user disruption.

[nated0g]

the server sdks being on these older dependency versions is causing quite a bit of pain for us as we attempt to migrate a couple large rust services to the smithy-rs server sdks from axum, which uses the newer http, hyper, etc,

How much work would you estimate there is to do to get this closed out? You mention that it would be better for client/server to go out in the same release, but presumably the server stuff could be worked on separately and put up on a branch

Happy to submit a PR if you can point us in the right direction.

[drganjoo]

Thanks for reaching out, and apologies for the delayed response.

We are actively working on migrating the client runtime crates to Hyper 1, which should be released in the next few weeks. Following that, we plan to update the code generator to support Hyper 1 for both client and server-side implementations in a single release.

We understand this dependency mismatch is causing difficulties for teams working across different ecosystems, particularly where some crates (like Axum) have already migrated to Hyper 1 while smithy-rs hasn't yet. We're working to minimize this transition period. Once the runtime crates are updated, we expect the code generator updates to progress quickly.

We appreciate your patience and offer to help. We'll keep this issue updated with our progress.

[ZackKanter]

We appreciate your patience and offer to help. We'll keep this issue updated with our progress.

Hi @drganjoo – just checking back to see if there was an update on this issue.

[drganjoo]

We plan on finishing this by the end of June 2025.

[ZackKanter]

We plan on finishing this by the end of June 2025.

Hi @drganjoo – wanted to check in to see if this was still slated to land soon. Any update is greatly appreciated – we have some internal items that are blocked on this, so we're hoping to update our internal roadmap timing.

[drganjoo]

Apologies for the delay! Currently working on this and targeting completion in about three weeks.

[landonxjames]

We are working on this on the client side as well. You can see some of the initial work in #4181