Skip to content

Add automated Maven Central release workflow - #295

Merged
lzsweb merged 1 commit into
mainfrom
chore/central-release-workflow
Nov 19, 2026
Merged

lzsweb merged 1 commit into
mainfrom
chore/central-release-workflow

Conversation

@lzsweb

@lzsweb lzsweb commented Nov 19, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Upgrade maven-gpg-plugin 1.6 → 3.2.7 with --pinentry-mode loopback so signing works in headless CI (1.6 hangs on the pinentry prompt).
  • Add autoPublish property (default false) wired into central-publishing-maven-plugin: local mvn deploy still uploads only; CI can opt into auto-publish via -DautoPublish=true.
  • Add .github/workflows/release.yml: on v* tags, gated by the maven-central environment (required reviewers). Guards: tag commit must be on main, pom version must match the tag, unit tests must pass. Then mvn deploy and auto-create a GitHub Release with generated notes.

Test plan

  • mvn test locally: 443 tests, 0 failures (3 skipped)
  • Configure maven-central environment secrets (CENTRAL_USERNAME / CENTRAL_PASSWORD / GPG_PRIVATE_KEY / GPG_PASSPHRASE) before first tag push
  • Dry-run: push a tag, approve, confirm deployment reaches VALIDATED on https://central.sonatype.com/publishing/deployments, then Drop

Upgrade maven-gpg-plugin to 3.2.7 with loopback pinentry for headless CI
signing, add an autoPublish switch (default false) to the central
publishing plugin, and publish on v* tags via a release workflow gated
by the maven-central environment approval.
@lzsweb
lzsweb merged commit 6f23dbe into main Nov 19, 2026
3 checks passed

This branch had an error being deployed

1 failed deployment
maven-central — fb6e10aa Deployed Nov 19, 2026 by lzsweb via publish #1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant