build(deps-dev): bump aws-lambda-powertools from 3.30.0 to 3.31.0

[dependabot]

Bumps aws-lambda-powertools from 3.30.0 to 3.31.0.

Release notes

Sourced from aws-lambda-powertools's releases.

v3.31.0

Summary

This release adds a new Circuit Breaker utility (in alpha) that stops your Lambda from sending requests to an unhealthy downstream and gives it time to recover. We also made parameter validation in the Event Handler more flexible, so any Pydantic Field annotation now works with any parameter type.

A huge thanks to everyone who helped shape the Circuit Breaker RFC and reviewed this release!

Circuit Breaker (alpha)

Docs

When a downstream service is failing, retries and Lambda's scaling only make it worse: more clients sending requests to something that is already down. The Circuit Breaker stops sending traffic to an unhealthy dependency, then probes it to see when it is safe to resume.

It ships as circuit_breaker_alpha on purpose. We want about a month of real-world feedback before we lock the public API and promote it to GA.

The smallest setup is a persistence store and a name. You wrap the function that makes the downstream call:

from aws_lambda_powertools.utilities.circuit_breaker_alpha import circuit_breaker
from aws_lambda_powertools.utilities.circuit_breaker_alpha.persistence import (
    CircuitBreakerDynamoDBPersistence,
)
from aws_lambda_powertools.utilities.typing import LambdaContext
persistence = CircuitBreakerDynamoDBPersistence(table_name="CircuitBreakerState")
@​circuit_breaker(name="payment-backend", persistence_store=persistence)
def charge(order: dict) -> dict:
return payment_api.charge(order)
def lambda_handler(event: dict, context: LambdaContext) -> dict:
return charge(event)

With no config, sensible defaults apply: open after 5 failures in a row, probe after 30s, close after 3 successes, and treat any exception as a failure. A few things make it a good fit for Lambda:

• It's free when healthy. The failure counter lives in memory, so a healthy circuit writes nothing. We only save state when it changes, so you pay during an incident, which is when you want to.
• State is shared across environments. Circuit state lives in DynamoDB, so the first environment that opens the circuit protects all the others.
• It fails open. If the state store can't be reached, the request goes through. A circuit breaker should never become the outage it's meant to prevent.
• One probe on recovery. When the timer is up, only one environment is selected to test the backend, instead of all of them sending requests at the same time.

When the circuit is open, you decide what happens to the rejected request with an on_circuit_open callback (buffer it, drop it, return a cached value), or let it raise CircuitBreakerOpenError. You can also watch state changes with an on_transition hook to emit your own metrics.

import json
from uuid import uuid4
from aws_lambda_powertools.utilities.circuit_breaker_alpha import circuit_breaker
</tr></table>

... (truncated)

Changelog

Sourced from aws-lambda-powertools's changelog.

[v3.31.0] - 2026-06-29

Features

• event_handler: support any Pydantic Field annotation in parameter (#8305)

Maintenance

• version bump

Commits

• 676c7cd chore: version bump
• 2c6b5e0 feat(event_handler): support any Pydantic Field annotation in parameter (#8305)
• 6c203ea chore(deps): bump redis from 7.4.0 to 8.0.1 (#8297)
• a9cffe4 chore(deps-dev): bump sentry-sdk from 2.62.0 to 2.63.0 (#8296)
• 29c5dc8 chore(deps-dev): bump boto3-stubs from 1.43.29 to 1.43.36 (#8295)
• e7e6745 feat: adding circuit breaker feature (#8266)
• 01e1e88 chore(ci): bump version to 3.30.0 (#8302)
• 697c8d1 chore(ci): layer docs update (#8303)
• See full diff in compare view

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud