You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dreamorosi opened this issue
Jul 25, 2023
· 2 comments
· Fixed by #1628
Assignees
Labels
commonsThis item relates to the Commons UtilitycompletedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
Since version 1.11.1 the commons package exposes the current Powertools version as a module. This is used in other utilities and can be used also from customers to append the Powertools version as a persistent attribute to the Logger (example).
We don't have yet an automated process to bump the version in the file, so we need to do it manually.
Why is this needed?
So that the version in the module is in line with the actual version released on npmjs.com.
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.
The text was updated successfully, but these errors were encountered:
dreamorosi
added
internal
PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
confirmed
The scope is clear, ready for implementation
commons
This item relates to the Commons Utility
labels
Jul 25, 2023
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.
commonsThis item relates to the Commons UtilitycompletedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
Summary
Since version
1.11.1
thecommons
package exposes the current Powertools version as a module. This is used in other utilities and can be used also from customers to append the Powertools version as a persistent attribute to the Logger (example).We don't have yet an automated process to bump the version in the file, so we need to do it manually.
Why is this needed?
So that the version in the module is in line with the actual version released on npmjs.com.
Which area does this relate to?
Other
Solution
No response
Acknowledgment
Future readers
Please react with 👍 and your use case to help us understand customer demand.
The text was updated successfully, but these errors were encountered: