Skip to content

Maintenance: bump version in commons prior to release #1627

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
1 of 2 tasks
dreamorosi opened this issue Jul 25, 2023 · 2 comments · Fixed by #1628
Closed
1 of 2 tasks

Maintenance: bump version in commons prior to release #1627

dreamorosi opened this issue Jul 25, 2023 · 2 comments · Fixed by #1628
Assignees
@dreamorosi
Labels
commons This item relates to the Commons Utility completed This item is complete and has been merged/shipped internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)

Comments

@dreamorosi
Copy link
Contributor

Summary

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.

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.
@dreamorosi 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
@dreamorosi dreamorosi self-assigned this Jul 25, 2023
@dreamorosi dreamorosi mentioned this issue Jul 25, 2023
Merged
9 tasks
@github-project-automation github-project-automation bot moved this from Working on it to Coming soon in Powertools for AWS Lambda (TypeScript) Jul 25, 2023
@github-actions
Copy link
Contributor

⚠️ 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.

@github-actions github-actions bot added pending-release This item has been merged and will be released soon and removed confirmed The scope is clear, ready for implementation labels Jul 25, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Jul 25, 2023 •
edited by dreamorosi
Loading

This is now released under v1.12.1 version!

@github-actions github-actions bot added completed This item is complete and has been merged/shipped and removed pending-release This item has been merged and will be released soon labels Jul 25, 2023
@dreamorosi dreamorosi moved this from Coming soon to Shipped in Powertools for AWS Lambda (TypeScript) Jul 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dreamorosi dreamorosi

Labels
commons This item relates to the Commons Utility completed This item is complete and has been merged/shipped internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
Projects
Powertools for AWS Lambda (TypeScript)
Status: Shipped
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore(commons): bump version prior to release aws-powertools/powertools-lambda-typescript
1 participant
@dreamorosi