-
Notifications
You must be signed in to change notification settings - Fork 153
Maintenance: v1 enters maintenance mode, scheduled end-of-life #2224
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
As part of this work we should mark all versions before 2.x as deprecated on npm using the method described here. |
This issue is now closed. Please be mindful that future comments 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. |
This is now released under v2.9.0 version! |
Summary
Important
On September 1st, 2024, Powertools for AWS Lambda (TypeScript) will end support for the v1.x release line and will no longer provide updates or releases.
Last week (03/07/2024) the next major version of Powertools for AWS Lambda (TypeScript) became generally available with the release 2.0.0.
In accordance to our versioning policy the v1.x release line officially enters maintenance mode and will reach end-of-support on September 1st, 2024.
During the maintenance mode we will continue to support the latest v1.x version via GitHub issues, Discord, and other channels as well as provide security fixes for issues affecting our codebase or direct runtime dependencies, but we won't back port any new feature added to v2.x versions.
If you are still using v1, we strongly recommend you to read our upgrade guide and update to the latest version.
Why is this needed?
So that customers can have clear expectations on timelines.
Which area does this relate to?
Governance
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: