Maintenance: refactor versioning process

[dreamorosi]

Summary

At the moment we have a single workflow that versions and publishes the packages to npm.

We should break down the workflows into two or more separate ones, possibly with human review at different steps.

Why is this needed?

To improve the visibility and security of each step.

we should also take this opportunity review the permissions associated with each step to make sure they apply the principle of least responsibility.

Which area does this relate to?

Automation

Solution

No response

Acknowledgment

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

Future readers

Please react with 👍 and your use case to help us understand customer demand.

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