Maintenance: fix post-release workflow

[dreamorosi]

Summary

The post-release workflow is executed after a new GitHub release has been published. Part of the workflow responsibility is to get all the closed issues labeled as status/pending-release, remove the label and announce the new release.

The workflow however is failing and we need to fix it.

Why is this needed?

So that the maintainers have less manual tasks after each release.

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.

[dreamorosi]

Also for some reason the status/pending-release was added to a PR, which shouldn't happen.

[github-actions]

⚠️ COMMENT VISIBILITY WARNING ⚠️

Comments on closed issues 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.