Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 12, 2026

Bumps aws-lambda-powertools from 3.23.0 to 3.24.0.

Release notes

Sourced from aws-lambda-powertools's releases.

v3.24.0

Summary

This release adds support for Lambda durable function replay in idempotency, a new parser model for DynamoDB Stream on-failure destinations, and a fix for batch processor. We've also dropped Python 3.9 support.

A super thanks to @​ConnorKirk for implementing the idempotency replay feature and @​exg for the batch processor fix and DynamoDB Stream parser model 🚀🌟

Idempotency: Allow durable functions to replay

Docs

AWS Lambda durable functions enable you to build resilient multi-step applications that can execute for up to one year while maintaining reliable progress despite interruptions. When a durable function resumes from a wait point or interruption, the system performs replay - running your code from the beginning but skipping completed checkpoints.

This release adds support for durable function replay in idempotency. When using the @idempotent decorator on lambda_handler, replay is automatically detected from the DurableContext - no manual configuration needed.

from aws_lambda_powertools.utilities.idempotency import idempotent, DynamoDBPersistenceLayer, IdempotencyConfig
persistence_layer = DynamoDBPersistenceLayer(table_name="idempotency_store")
config = IdempotencyConfig(event_key_jmespath="body")
@​idempotent(config=config, persistence_store=persistence_layer)
def lambda_handler(event, context):
# Replay is automatically detected when context is a DurableContext
# During replay, INPROGRESS records are handled gracefully
return {"statusCode": 200}

DynamoDB Stream On-Failure Destination parser model

Docs

A new parser model DynamoDBStreamLambdaOnFailureDestinationModel is now available for parsing DynamoDB Stream on-failure destination events.

from aws_lambda_powertools.utilities.parser import parse
from aws_lambda_powertools.utilities.parser.models import DynamoDBStreamLambdaOnFailureDestinationModel
def lambda_handler(event, context):
parsed = parse(event=event, model=DynamoDBStreamLambdaOnFailureDestinationModel)
batch_info = parsed.ddb_stream_batch_info
print(f"Failed batch from shard: {batch_info.shard_id}")
print(f"Stream ARN: {batch_info.stream_arn}")

Changes

... (truncated)

Changelog

Sourced from aws-lambda-powertools's changelog.

[v3.24.0] - 2026-01-05

Maintenance

  • version bump
  • ci: remove daily changelog rebuild schedule (#7897)

Commits
  • d561d12 chore: version bump
  • 608df1b chore(ci): remove daily changelog rebuild schedule (#7897)
  • 33f2c8f docs(homepage): reorganize homepage and create dedicated installation page (#...
  • c30d9d4 chore(ci): remove automated pre-release schedule (#7894)
  • 2696e54 chore(deps-dev): bump boto3-stubs from 1.42.19 to 1.42.21 (#7892)
  • 10226f9 chore(deps): bump the github-actions group with 2 updates (#7893)
  • f0102a9 chore(ci): improve dependabot workflow to reduce noise (#7890)
  • 787bcae chore(deps-dev): bump boto3-stubs from 1.42.17 to 1.42.19 (#7873)
  • 6721e91 docs(readme): update features list and improve readability (#7889)
  • 26abeee chore(deps-dev): bump aws-cdk-aws-lambda-python-alpha from 2.232.2a0 to 2.233...
  • Additional commits viewable in compare view

Dependabot compatibility score

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 merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @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)

Bumps [aws-lambda-powertools](https://github.com/aws-powertools/powertools-lambda-python) from 3.23.0 to 3.24.0.
- [Release notes](https://github.com/aws-powertools/powertools-lambda-python/releases)
- [Changelog](https://github.com/aws-powertools/powertools-lambda-python/blob/develop/CHANGELOG.md)
- [Commits](aws-powertools/powertools-lambda-python@v3.23.0...v3.24.0)

---
updated-dependencies:
- dependency-name: aws-lambda-powertools
  dependency-version: 3.24.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file python Pull requests that update python code labels Jan 12, 2026
@sonarqubecloud
Copy link

@github-actions github-actions bot merged commit 40901f1 into develop Jan 12, 2026
6 checks passed
@github-actions github-actions bot deleted the dependabot/pip/aws-lambda-powertools-3.24.0 branch January 12, 2026 03:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file python Pull requests that update python code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants