Maintenance: docs versioning & labels

[dreamorosi]

Summary

While working on the docs I have realized that the when we touched the workflow that publishes the docs a couple of months ago we have broken the labeling/versioning.

Currently the docs that should be published as staging/dev when the docs are merged are not selectable, and the version label has changed convention which conflicts with the ordering of the labels in the docs dropdown.

Why is this needed?

Because currently we are unable to:

• Select the stage label to see the docs once they are merged
• Select the labels in chronological order with most recent on top (currently v1.8.0 which is latest is towards the bottom of the dropdown)

Which area does this relate to?

Automation

Solution

Ideally, we should get to a state that has:

• All the version numbers without the v prefix - this way we maintain the ordering in the dropdown with the more recent on top
• Remove all orphan labels like dev, main, and the ones that start with v (i.e. v1.7.0 and v1.8.0)
• When docs are merged to main, they are published under stage, which should appear in the dropdown as last (at the bottom)

Acknowledgment

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

Future readers

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

[dreamorosi]

I'll be working on this one, we can't rebuild the docs until this is fixed.

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