Maintenance: introduce nox to test optional dependencies

heitorlessa commented 3 weeks ago

Why is this needed?

Today's release suffered a regression due to static typing accidentally requiring an optional dependency for customers.

We must not make any release until we have a safeguard to prevent this in the future.

https://github.com/aws-powertools/powertools-lambda-python/issues/4498

Update with task list - 14/06

[x] #4519
[x] #4520
[x] #4521
[x] #4522
[x] #4523
[x] #4553
[x] #4562
[x] #4554
[x] #4555
[x] #4561
[x] #4556
[x] #4560
[x] #4557
[x] #4558
[x] #4559
[x] #4573

Which area does this relate to?

No response

Solution

Use nox, or create new workflows where we test bare dependencies, and every optional dependencies.

Acknowledgment

[X] This request meets Powertools for AWS Lambda (Python) Tenets
[ ] Should this be considered in other Powertools for AWS Lambda languages? i.e. Java, TypeScript, and .NET

leandrodamascena commented 3 weeks ago

Assigning to me.

leandrodamascena commented 3 weeks ago

Introducing nox requires a lot of changes to our tests and can easily become a PR with hundreds of lines of changes. So I'll break this down into small PRs to make reviewing easier.

github-actions[bot] commented 2 weeks ago

⚠️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.

aws-powertools / powertools-lambda-python