Release 2.0.0

[phipag]

Summary

This issue tracks releasing version 2.0.0 of Powertools for AWS Lambda (Java).

• Prepare project configuration and workflows for v2 release
  • chore(v2): Remove rule preventing production release of 2.0.0 #1867
  • fix(ci): Checkout repo on doc release #1869
  • fix: Add maven central required information to pom.xml #1871
  • fix: Add required maven central properties #1872
• Perform release to Maven Central
  • Release workflow ✅ https://github.com/aws-powertools/powertools-lambda-java/actions/runs/15606044104/job/43956232624
  • Published ✅ https://central.sonatype.com/artifact/software.amazon.lambda/powertools-parent/2.0.0
• Re-organize GitHub branches
  • Renamed main to 1.x.x
  • Renamed v2 to main to make it the new default
• 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 v2 branch
• Update documentation
  • Maintenance: Version the documentation #1239
• Publish release notes to GitHub
  • Published ✅ https://github.com/aws-powertools/powertools-lambda-java/releases/tag/v2.0.0
• 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