ci: Add Maven Central release workflow with GitHub Release

[jeffjensen]

What

Adds a Release to Maven Central workflow, with the supporting jdk-setup action change.

• Triggered by pushing a plugin-* tag.
• Deploys GPG-signed artifacts to Maven Central via the release profile.
• Publishes a GitHub Release for the tag with auto-generated notes, in a separate job that is granted contents: write only after the deploy succeeds — keeping that permission away from the credential and signing step.
• Verifies the tag matches the POM project.version before deploying, and titles the Release from that resolved version, so a mistyped tag cannot publish one version while announcing another.
• Extends the jdk-setup composite action to optionally supply Maven Central and GPG credentials. Existing callers pass no inputs and are unaffected.

Required repository configuration

A release environment containing these secrets:

• GPG_PRIVATE_KEY
• GPG_PASSPHRASE
• CENTRAL_USERNAME
• CENTRAL_TOKEN

🤖 Generated with Claude Code

https://claude.ai/code/session_0133BgD2ro4ZJh1TaXHrZSff

[coderabbitai]

Warning

Review limit reached

@jeffjensen, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 58 minutes and 44 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 1bdab1d6-ee20-4ee6-b855-0a2878c04c3f

📥 Commits

Reviewing files that changed from the base of the PR and between 81515f2 and fadd389.

📒 Files selected for processing (2)

• .github/actions/jdk-setup/action.yml
• .github/workflows/release.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ci/release-workflow

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}