ci: Publish to Maven Central workflow; java/PUBLISHING.md - #48
Merged
Conversation
…release's natives, sign, stage on the Central Portal); java/PUBLISHING.md The release profile's autoPublish becomes the property central.autoPublish (default false) so the workflow's input can choose between staging the deployment for review and releasing on validation. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YG6wFApZpg2xe61EmKhaSZ
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
.github/workflows/publish-maven.yml: dispatched with a release tag, it checks the POM version against the tag, fetches the four native libraries from that release's assets (the Release workflow's recipe), builds the jar with them, signs everything with the GPG key from the repository secrets and uploads the bundle throughcentral-publishing-maven-plugin. By default the deployment is validated and left staged on the Central Portal for a human to publish or drop; thepublishinput releases automatically. The POM's hardcodedautoPublishbecomes the propertycentral.autoPublish(default false) so the input can drive it.java/PUBLISHING.mdrecords the one-time setup (namespace verification, user token, signing key, themaven-centralenvironment) and the per-release steps;java/README.mdpoints at it.Needs, before the first run: secrets
CENTRAL_USERNAME,CENTRAL_PASSWORD,GPG_PRIVATE_KEY,GPG_PASSPHRASE; themaven-centralenvironment; theorg.adbcbridgenamespace verified.🤖 Generated with Claude Code
https://claude.ai/code/session_01YG6wFApZpg2xe61EmKhaSZ