Bump lambda_runtime from 1.0.2 to 1.1.2 in /s3-uploader/runtimes/rust_on_provided_al2023

[dependabot]

Bumps lambda_runtime from 1.0.2 to 1.1.2.

Release notes

Sourced from lambda_runtime's releases.

v1.1.2

Fixed

• fix handling of null groupConfiguration (#1130)

Other

• release (#1118)

v1.1.1

Thank you to all the contributors who helped make this release possible. We appreciate your time, effort, and passion for the Rust Lambda community. ❤️

Lambda Managed Instances

The runtime now supports Lambda Managed Instances via the concurrency-tokio feature flag (previously experimental-concurrency). Lambda Managed Instances allow multiple concurrent requests to be processed within a single execution environment. When AWS_LAMBDA_MAX_CONCURRENCY is set, the runtime spawns multiple independent long-poll workers to handle concurrent invocations. If the env var is unset or <= 1, it falls back to sequential behavior automatically. This lets you use the same handler for both classic Lambda and Lambda Managed Instances. (#1067)

[dependencies]
lambda_runtime = { version = "1.1", features = ["concurrency-tokio"] }

lambda_runtime::run_concurrent(service_fn(my_handler)).await?;

For a complete working example, see examples/basic-lambda-concurrent. For detailed guidance on building functions for multi-concurrency, including shared state patterns and database connection pools, see the Rust runtime for Lambda Managed Instances documentation.

We would like also to involve the community in a broader discussion about improving our approach on multiconcurrency. You can find the discussion in (#1120)

lambda_runtime - 1.1.1

Added

• (lambda-managed-instances) log non-2xx Lambda Runtime API responses with status and body (#1109)
• tenant ID propagation for multi-tenant Lambda use cases. The tenant_id is available in the context.tenant_id field (Option<String>) and is automatically extracted from the lambda-runtime-aws-tenant-id header when present (#1082)
• Add builder pattern support for event response types (#1090)

Fixed

• (test) fix test_concurrent_structured_logging_isolation (#1121)

Changed

• MSRV updated from 1.82.0 to 1.84.0, enabled MSRV-aware resolver (#1078)
• X-Ray trace ID now sourced from Context instead of environment variables (#1067)

Other

• (lambda-managed-instances) add tokio_unstable to known cfgs to avoid linter warns (#1095)

... (truncated)

Commits

• 45850d4 chore: release (#1132)
• bafe106 fix handling of null groupConfiguration (#1130)
• 6f305bb chore: fix dev dep dependency (#1126)
• b16f532 dmelfi/fix issue with dev dep (#1124)
• e77825c Fix deployment issue in aws_lambda_event because of dev dep (#1123)
• 6d5f3de chore: release (#1118)
• 0aa6c8e fix(test): fix test_concurrent_structured_logging_isolation (#1121)
• 7f66cde Resolve inconsistencies in .gitignore making release-plz fail (#1117)
• b5e978e Revert change in releaze-plz toml breaking the github action (#1116)
• 114b212 test(all) Add concurrent Lambda invocation tests (#1112)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)