Maintenance: create v2 pre-release workflow

[dreamorosi]

Summary

Currently our automation is prepared to handle only one release line at the time. With the start of the work on the next major version we need to prepare to make pre-releases alongside the current 1.x version.

As part of this issue we should create a workflow that allows to publish to the npm registry the v2 pre-release versions of our utilities. The versions should be tagged as next and follow this convention:

• 2.0.0-alpha.0
• 2.0.0-alpha.1
• 2.0.0-alpha.2
• 2.0.0-beta.0
• 2.0.0-beta.1
• 2.0.0-rc.0

We won't be creating git tags for these releases nor change logs, however we will try to publish docs under the next alias as part of another PR.

Why is this needed?

This is needed in order to give customers access to the new releases as soon as possible. This way they can start testing the changes and optionally provide comments/feedback on them.

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

Comments on closed issues 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.