Maintenance: Verify release version is valid before proceeding

[heitorlessa]

Summary

As per discussion, we can be extra careful with the value of the release tag. While there isn't a scenario where this could be null, it could be a non-semantic value.

Why is this needed?

Prevent release workflow from failing or having unintended version published.

Which area does this relate to?

Automation

Solution

We could verify the value follows semantic versioning and is not null. Alternatively, we could also have a manual approval step for when the workflow runs.

Acknowledgment

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

[heitorlessa]

We've moved towards a two-person release as all activities are automated now. This gives us enough safety and ensures our messaging is adequate to what we're releasing from more than one point of view.

[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.