Add server and GPG configuration to setup-java in release workflow

[Copilot]

Description

Adds Maven Central server authentication and GPG signing configuration to the setup-java step in .github/workflows/release.yml. Without these parameters, deployments to Maven Central cannot authenticate or sign artifacts.

Resolves #(issue)

Changes

Added five configuration parameters to the 'Set up JDK 25' step:

• server-id: central - Maven Central repository identifier
• server-username: MAVEN_USERNAME - Maven authentication username from environment
• server-password: MAVEN_PASSWORD - Maven authentication password from environment
• gpg-private-key: ${{ secrets.MAVEN_GPG_PRIVATE_KEY }} - GPG private key from secrets
• gpg-passphrase: MAVEN_GPG_PASSPHRASE - GPG passphrase from environment

Configuration mirrors existing pattern in maven-publish.yml for consistency.

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>[Enhancement]: Add server and GPG configuration options to setup-java in release workflow</issue_title>
<issue_description>### What

Add the following configuration parameters to the 'Set up JDK 25' 'setup-java' step in .github/workflows/release.yml:

• server-id: central
• server-username: MAVEN_USERNAME
• server-password: MAVEN_PASSWORD
• gpg-private-key: ${{ secrets.MAVEN_GPG_PRIVATE_KEY }}
• gpg-passphrase: MAVEN_GPG_PASSPHRASE

These should be added to ensure proper authentication and signing of artifacts when deploying to Maven Central.

Why

This enhancement ensures that the build and release workflow correctly authenticates and signs releases for Maven Central. Without these parameters, deployment can fail or be insecure. Including the required server and GPG configuration keys aligns with recommended best practices for publishing Java artifacts.

Notes

Reference workflow file: .github/workflows/release.yml.
Suggested location: 'Set up JDK 25' (setup-java) step.
No other changes anticipated unless new deployment requirements arise.</issue_description>

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

• Fixes [Enhancement]: Add server and GPG configuration options to setup-java in release workflow #363

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[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