Bug: regression in pip release that included mypy-boto3-* dev dependencies

[tb102122]

Is this related to an existing feature request or issue?

No response

Which AWS Lambda Powertools utility does this relate to?

Other

Summary

Why do we need the dependency in the final release build?

mypy-boto3-cloudwatch = "^1.24.0"
mypy-boto3-lambda = "^1.24.0"
mypy-boto3-xray = "^1.24.0"

Use case

reduce package size

Proposal

remove dependency

Out of scope

n/a

Potential challenges

n/a

Dependencies and Integrations

No response

Alternative solutions

No response

Acknowledgment

• This feature request meets Lambda Powertools Tenets
• Should this be considered in other Lambda Powertools languages? i.e. Java, TypeScript

[boring-cyborg]

Thanks for opening your first issue here! We'll come back to you as soon as we can.

[heitorlessa]

hey @tb102122 that's a bug, this should have been a dev dependency like other mypy types we have; an oversight from our part when merging @mploski E2E testing PR: https://github.com/awslabs/aws-lambda-powertools-python/blame/develop/pyproject.toml#L29

We'll make a patch release in the next 2 hours to address it

[tb102122]

Great thanks!

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

This issue is now closed. Please be mindful that future comments are hard for our team to see.

If you need more assistance, please either tag a team member or 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.

[github-actions]

This is now released under 1.26.5 version!

[heitorlessa]

@tb102122 now live on PyPi and SAR (v1.26.5) -- Lambda Layer might take a few hours to update across regions.

Huge thanks again @tb102122