Maintenance: review changelog generation

[dreamorosi]

Summary

As of now we use lerna to version the packages and generate their respective changelog.

The automation is not working correctly and the changelog files are populated but none of the changes is actually reflected. This means maintainers have to go back to each changelog file and manually add the items that changed for each release.

We should review this and fix the issue.

Why is this needed?

So that we can automate the task again and reduce the overhead on maintainers when releasing a new version.

Which area does this relate to?

No response

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.

[dreamorosi]

It seems that versioning is also having issues, even though we are expecting minor version bumps, we only always get patch.

[github-actions]

⚠️ COMMENT VISIBILITY WARNING ⚠️

This issue is now closed. Please be mindful that future comments 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.

[github-actions]

This is now released under v2.1.0 version!