[Konboi]

Why

Maven releases currently require manual version preparation, tagging, and Central Portal publishing. The repository migration also left the POM SCM URL pointing at the retired repository location.

What

• Add tagpr to create release pull requests, tags, and GitHub Releases from main.
• Publish signed Maven artifacts to Central Portal when a launchable-testng tag is pushed.
• Update the POM SCM URL to the CloudBees repository.
• Document required GitHub Actions permissions and Maven Central and GPG secrets.
• Update CI actions to v4 for the current GitHub Actions runtime.

Validation

• actionlint
• Maven clean verify, including GPG signing and source and javadoc artifact generation

Please Review Here

Repository administrators must configure the documented secrets and allow GitHub Actions to create pull requests before the first automated release.