Maintenance: fix docs publishing during release

[dreamorosi]

Summary

Note
This is not related to #1490, the issue happens when publishing to a different destination.

When making a release, the very last step consists in rebuilding the docs and deploying them on GitHub Pages with the update ARNs of the public Lambda Layers for Powertools.

The workflow is currently failing with an error that suggests that mike is not able to push the latest tag due to it existing already.

We need to investigate and understand why this is happening and fix it.

Why is this needed?

So that we can make an automated release that includes all the steps.

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.