Bug: Release workflow does not update version in documentation

[phipag]

Summary

When running the release workflow the documentation website gets correctly deployed and the versions.json file also gets updated.

The issue is that the mkdocs.yaml file does not get updated with the newly released version making all code examples and installation instructions using a stale project version.

Why is this needed?

This is needed to provide correct code samples and installation instructions inline with the documentation version to customers.

Which area does this relate to?

Automation

Solution

No response

Acknowledgment

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