Maintenance: add forcePublish flag to lerna config

[am29d]

Summary

In the last release the versioning workflow did not bump the parser package, which is not what we expected. After going through all the commits between the releases it turned out that for all the releases before that, we had commits that were picked up by lerna and versioning worked as expected. These are usually dependabot or repo wide changes, i.e. new customer reference, that would affect all packages.

In the last two weeks there was not a single commit to the parser package, and thus lerna versioning did not bump it.

To avoid that in the future, we should add forcePublish flag to the lerna.json configuration.

Why is this needed?

So lerna bumps all package version regardless of commit history.

Which area does this relate to?

Automation

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.

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