-
Notifications
You must be signed in to change notification settings - Fork 156
[Support Lambda Powertools]: tecRacer GmbH & Co. KG #1650
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.
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
Comments
Hi @hfahlbusch thank you so much for this issue and for supporting the project, we really appreciate it! I'll add the name to the READMEs and docs in a PR later this week and report back here once it's published :) |
Thanks @dreamorosi ! |
|
I have added the name & link to the docs (if not showing yet wait a few moments or clear your browser cache) as well as the readme files of the utilities. The new version of the files will be published on npmjs.com on the next Powertools release. Thank you again for supporting the project, it means a lot for us! |
This is now released under v1.13.0 version! |
Organization Name
tecRacer GmbH & Co. KG
Your Name
Helge Fahlbusch
Your current position
Software Quality Specialist
(Optional) Company logo
https://www.tecracer.com/wp-content/uploads/2022/01/tR_RGB_White_b.svg
(Optional) Use case
No response
Also using other Powertools for AWS Lambda languages?
The text was updated successfully, but these errors were encountered: