Maintenance: Version the documentation

[jeromevdl]

Summary

Currently the documentation is not versioned, unlike Python and Typescript. We should version the doc to be consistent with other runtimes and to prepare for v2.

Why is this needed?

• Consistency with other runtimes
• Keep history of changes (doc for a specified version)
• Preparing v2 (we'll need to have both v1 and v2 available at least)

Which area does this relate to?

Automation, Governance

Solution

See how python is doing: https://github.com/aws-powertools/powertools-lambda-python/blob/develop/.github/workflows/reusable_publish_docs.yml. Check with @sthulb / @heitorlessa.

Acknowledgment

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

[sthulb]

Python/TS uses a python package called mike to version docs – but in our post GH Pages world, we might want to look into doing this differently.

[kozub]

I'm going to take care of it.