Switch Maven publishing workflow to Central Publisher Portal

[Copilot]

Description

Migrates Maven publishing from legacy OSSRH Nexus staging to the Central Publisher Portal API. This modernizes the release infrastructure without affecting artifact consumers.

Resolves #328

Changes

Maven Configuration (pom.xml)

• Replace nexus-staging-maven-plugin (1.7.0) → central-publishing-maven-plugin (0.6.0)
• Update distributionManagement to Central Portal API endpoint
• Change server ID: ossrh → central
• Configure autoPublish=true and waitUntil=published for automated releases

GitHub Workflows

• Update maven-publish.yml and maven-publish-snapshot.yml server-id from ossrh to central
• Keep existing secret names: Continue using OSSRH_USERNAME and OSSRH_TOKEN (no secret changes required)

Required Action

No secret updates required! The existing GitHub secrets will work with the Central Publisher Portal:

• OSSRH_USERNAME and OSSRH_TOKEN remain unchanged and will be used for Central Portal authentication
• Existing GPG secrets (MAVEN_GPG_PRIVATE_KEY, MAVEN_GPG_PASSPHRASE) remain unchanged

Checklist:

• Public methods are documented
• Public methods are tested
• New and existing tests pass when run locally
• There are no new warnings or errors

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[Chore]: Switch Maven publishing workflow to Central Publisher Portal</issue_title>
<issue_description>### What

Switch the Maven publishing workflow to use the Central Publisher Portal as documented at https://central.sonatype.org/publish/publish-portal-maven/. Update automation and documentation as needed.

Why

The Central Publisher Portal offers a unified, reliable, and modern flow for publishing Maven artifacts to Maven Central. This change will improve maintainability and future-proof the release process.

Notes

Reference documentation: https://central.sonatype.org/publish/publish-portal-maven/
Please update automation scripts and documentation to reflect the new workflow. No breaking changes expected for consumers.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes [Chore]: Switch Maven publishing workflow to Central Publisher Portal #328

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[thomasturrell]

@copilot I don't want to change the secrets key names at this point.

[Copilot]

@copilot I don't want to change the secrets key names at this point.

Done. Reverted to using existing secret names OSSRH_USERNAME and OSSRH_TOKEN in both workflows. The server-id remains changed to central as required for the Central Publisher Portal. (commit 1de6382)

[thomasturrell]

@copilot remove the release documentation. We will add it in later. Free free to create a core issue for it.

[Copilot]

@copilot remove the release documentation. We will add it in later. Free free to create a core issue for it.

Done. Removed RELEASE.md in commit b259258.

I don't have permissions to create GitHub issues, but here's the suggested issue content:

Title: [Chore]: Add release documentation for Central Publisher Portal

Description:

What

Add comprehensive release documentation explaining how to publish releases using the Central Publisher Portal.

Why

The project now uses the Central Publisher Portal for Maven publishing (as of PR #329), but documentation about the release process is needed for maintainers.

Notes

Documentation should cover:

• Prerequisites and required GitHub secrets (OSSRH_USERNAME, OSSRH_TOKEN, GPG keys)
• Step-by-step release instructions using GitHub Actions
• Snapshot publishing process
• Manual release fallback procedure
• Migration notes from legacy OSSRH
• Links to official Central Portal documentation

Reference: https://central.sonatype.org/publish/publish-portal-maven/

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud