Maintenance: restore changelog creation

[dreamorosi]

Summary

For each release, together with the release notes, we also publish the changes for each package in their respective changeling file (i.e. packages/logger/CHANGELOG.md).

For the last two releases the changelog files didn't get updated.

Why is this needed?

So that customers can have a breakdown of all the changes in a file related to the package.

However the fact that nobody reported this might suggest not many people are actually looking at these files. The same info, plus additional explanations are already available in the release notes.

Which area does this relate to?

No response

Solution

We need to investigate further, but the releases stopped being generated after we dropped support for Node.js 14 which is also when we upgraded to lerna v7.0.x. The release notes don't have anything related to this, so it's not clear why it stopped adding updates to the files.

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]

As evidenced by #2100 the changelog creation is working again, so there's no fix to apply.

I'll open a PR to manually write the change log for the 2-3 missing releases.

[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 v1.18.1 version!