[lambda-http-0.8.2] unresolved imports

[aesterline]

When upgrading to lambda-http-0.8.2, I get the following error when trying to run cargo check. I do not have lambda_runtime in my Cargo.toml dependencies. I use the re-exported version of lambda_runtime in my code when it is required. (use lambda_http::lambda_runtime::{run as lambda_run, service_fn, LambdaEvent};)

error[E0432]: unresolved imports `lambda_runtime::FunctionResponse`, `lambda_runtime::MetadataPrelude`, `lambda_runtime::StreamResponse`
  --> /Users/home/.cargo/registry/src/index.crates.io-6f17d22bba15001f/lambda_http-0.8.2/src/streaming.rs:10:56
   |
10 |     self, service_fn, tower, tower::ServiceExt, Error, FunctionResponse, LambdaEvent, MetadataPrelude, Service,
   |                                                        ^^^^^^^^^^^^^^^^               ^^^^^^^^^^^^^^^ no `MetadataPrelude` in the root
   |                                                        |
   |                                                        no `FunctionResponse` in the root
11 |     StreamResponse,
   |     ^^^^^^^^^^^^^^ no `StreamResponse` in the root

[calavera]

Ugh, I'm sorry about that. The latest version of lambda_http requires the latest version of lambda_runtime, but if it's not explicitly set, the code won't compile.

I have a fix for this in #723, but if you don't want to wait for it, your code should compile if you add lambda_runtime = "0.8.3" to your dependencies.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for the maintainers of this repository to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[calavera]

I've published a new version that fixes this problem: https://crates.io/crates/lambda_http/0.8.3
I've also yanked 0.8.2 to prevent future installs.