Migrate release publishing from OSSRH to Central Publisher Portal

[diemol]

Summary

• Sonatype has fully decommissioned the legacy OSSRH host (oss.sonatype.org), which caused the release workflow to fail with a 404 during deploy.
• Replace nexus-staging-maven-plugin with org.sonatype.central:central-publishing-maven-plugin:0.11.0 targeting the new Central Publisher Portal (central.sonatype.com), and drop the now-unneeded distributionManagement block.
• Update release.yml to use the central server id and CENTRAL_USERNAME/CENTRAL_TOKEN secrets instead of OSSRH_USERNAME/OSSRH_TOKEN.

Before merging / releasing

• Generate a User Token at central.sonatype.com (Account → Generate User Token)
• Add repo secrets CENTRAL_USERNAME and CENTRAL_TOKEN with those values

Test plan

• mvn validate passes with the updated pom.xml
• Run the "Release to Maven Central" workflow once the new secrets are in place to confirm publishing succeeds end-to-end

🤖 Generated with Claude Code

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}