Fix Maven Central upload workflow

[fabiogouw]

Summary

This PR fixes the Maven Central upload workflow after the first run exposed an incomplete PGP signing setup.

What changed

• added JRELEASER_GPG_PUBLIC_KEY to the release workflow because JReleaser PGP memory mode requires the public key in addition to the private key and passphrase
• kept the Maven Central release workflow available in both modes: automatic on v* tag push and manual via workflow_dispatch with a release_tag input
• updated the README release instructions to document the required public key secret and the manual dispatch flow
• restricted the draw.io export workflow to branch pushes so it no longer runs when a release tag is pushed

How to use

GitHub Actions

Configure these repository secrets before running the release workflow:

• MAVEN_CENTRAL_USERNAME
• MAVEN_CENTRAL_PASSWORD
• JRELEASER_GPG_PUBLIC_KEY
• JRELEASER_GPG_SECRET_KEY
• JRELEASER_GPG_PASSPHRASE

The workflow can be triggered in two ways:

1. Push a tag that matches v*.
2. Run the workflow manually and provide the release_tag input.

In both cases the workflow uploads the deployment to Maven Central in UPLOAD mode, and the final publish step must still be confirmed manually in the Central Portal.

Local run

Export the same Maven Central and JReleaser signing variables locally, plus GITHUB_TOKEN, then run:

./gradlew :spark-aws-messaging:publishToMavenCentral

If you want to force upload-only mode locally, use:

JRELEASER_MAVENCENTRAL_STAGE=UPLOAD ./gradlew :spark-aws-messaging:publishToMavenCentral

[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