Skip to content

Maintenance: introduce nox to test optional dependencies #4501

Closed
@heitorlessa

Description

@heitorlessa

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.

#4498

Update with task list - 14/06

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

  • Should this be considered in other Powertools for AWS Lambda languages? i.e. Java, TypeScript, and .NET

Activity

leandrodamascena

leandrodamascena commented on Jun 13, 2024

@leandrodamascena
Contributor

Assigning to me.

leandrodamascena

leandrodamascena commented on Jun 14, 2024

@leandrodamascena
Contributor

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

github-actions commented on Jun 20, 2024

@github-actions
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

Status

Shipped

Relationships

None yet

    Development

    No branches or pull requests

      Participants

      @heitorlessa@leandrodamascena

      Issue actions

        Maintenance: introduce nox to test optional dependencies · Issue #4501 · aws-powertools/powertools-lambda-python