Maintenance: Run pydantic v2 workflow only for features using pydantic

[heitorlessa]

Why is this needed?

Our CI times doubled as GH has a limit of concurrent workflows run, increasing our lead time.

Which area does this relate to?

No response

Solution

Short-term: change paths in Pydantic V2 workflow to only use Event Handler, Parser, and Batch.

Medium-term: if CI time continues to be high, we use nox like solution to dynamically swap Pydantic version at runtime (no additional workflow).

Long-term: Launch v3 with Pydantic v2 and drop v1.

Acknowledgment

• 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]

Hey @heitorlessa! Our tests takes +-30s to complete and I think we can start removing lint/static checking. Let me send the PR to check this.

[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 2.27.1 version!