Bump lambda_runtime from 1.0.2 to 1.2.1 in /s3-uploader/runtimes/rust_on_provided_al2

[dependabot]

Bumps lambda_runtime from 1.0.2 to 1.2.1.

Release notes

Sourced from lambda_runtime's releases.

v1.2.1

Other

• (deps) update opentelemetry-semantic-conventions requirement (#1147)

v1.2.0

Added

• Add VPC Lattice as an upstream source for lambda-http (#1136)

Fixed

• (lambda-http) into_api_gateway_v2_request joins cookies with "; " (#1143)

Other

• Added builders pass-through feature to enable aws_lambda_events/builders (#1146)

v1.1.3

Other

• remove non exhaustive from time structs (#1138)

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.

... (truncated)

Commits

• 63c45d4 chore: release v1.2.1 (#1149)
• 55eb61e build: release-plz could cause multiple run-integration-test workflows to run...
• 3318f9e chore(deps): update opentelemetry-semantic-conventions requirement (#1147)
• 0123749 chore: release v1.2.0 (#1144)
• f79e7c6 [lambda_http]: Added builders pass-through feature to enable `aws_lambda_ev...
• 6297eba chore(deps): bump yaml and aws-cdk-lib (#1145)
• cb8fbb0 feat: Add VPC Lattice as an upstream source for lambda-http (#1136)
• 301e3cd fix(lambda-http): into_api_gateway_v2_request joins cookies with "; " (#1143)
• e397be4 chore: release v1.1.3 (#1139)
• 9e34f52 chore(deps): bump yaml and aws-cdk-lib in /examples/http-axum/cdk (#1140)
• 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)