-
Notifications
You must be signed in to change notification settings - Fork 162
Open
Labels
confirmedThe scope is clear, ready for implementationThe scope is clear, ready for implementationinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
Description
Summary
In #4201 we introduced a new shared GitHub Action that comes from the aws-powertools/actions
repo and that bumps the version of the packages in the repo as well as generating change log files for each package.
The action however is failing at one of the last steps when creating the PR with the changes, see log here.
Why is this needed?
So that we can use the new make-version.yml
workflow.
Which area does this relate to?
Automation
Solution
Once aws-powertools/actions#189 is merged and version 1.2.0 is released, update the hash of the version-n-changelog
GitHub Action in the make-version.yml
workflow to use the latest version.
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.
Metadata
Metadata
Assignees
Labels
confirmedThe scope is clear, ready for implementationThe scope is clear, ready for implementationinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
Type
Projects
Status
Pending review