Maintenance: 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

[phipag]

The problem seems to be that when the docs workflow runs it clones the repository that does not have the version bump PR merged from the version_seal step. This is why the docs versions is not bumped as part of the release workflow.

[phipag]

I noticed that the changelog updating is a separate problem. We are missing a workflow action to update this. I will create a follow-up issue to onboard with https://github.com/aws-powertools/actions/tree/main/.github/actions/version-n-changelog