Closed
1 of 1 issue completedDescription
Summary
This issue tracks releasing version 2.0.0 of Powertools for AWS Lambda (Java).
- Prepare project configuration and workflows for
v2release - Perform release to Maven Central
- Re-organize GitHub branches
- Renamed
mainto1.x.x - Renamed
v2tomainto make it the new default
- Renamed
- Update workflows to be compatible with restructured GitHub branches (chore(ci): Update workflows to make v2 the default #1888)
- Do not auto-publish release notes
- Update workflows to remove references to
v2branch
- Update documentation
- Publish release notes to GitHub
- Announce deprecation plan for v1
- Update versioning policy page ✅ docs: Announce deprecation of v1 #1896
- Create pinned GH issue with plan ✅ Maintenance: v1 enters maintenance mode, scheduled end-of-life #1895
Why is this needed?
The new version will come with new features and re-designed utilities. This also includes breaking changes in the interface of some utilities requiring a major version bump.
Which area does this relate to?
Other
Solution
No response
Acknowledgment
- This request meets Powertools for AWS Lambda (Java) Tenets
- Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, TypeScript
Sub-issues
Metadata
Metadata
Labels
Type
Projects
Status
Shipped