fix(release): auto-release to Maven Central (automaticRelease = true)#45
Conversation
Change publishToMavenCentral() → publishToMavenCentral(automaticRelease = true) so a validated deployment is published to Maven Central automatically after upload, with no manual "Publish" click in the Central Portal UI. Verified the build still configures (`:packages:sdk:help`). Note: this only takes effect once the upstream signing blocker is resolved (GPG_PRIVATE_KEY secret) — it does not by itself fix the current signMavenPublication failure. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the Maven Central publishing configuration in packages/sdk/build.gradle.kts to enable automatic releases (automaticRelease = true). Feedback suggests ensuring consistency by applying this change to the core module as well to prevent partial releases, and updating the RELEASE.md documentation to reflect the new automated process.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
…ad PGP secret key") A local `:packages:sdk:publishToMavenLocal` with the real signing key and NO keyId signs successfully (signMavenPublication runs, .asc files produced). CI sets ORG_GRADLE_PROJECT_signingInMemoryKeyId from GPG_KEY_ID and fails with "Could not read PGP secret key". The keyId is optional — the plugin derives the key from the armored block — so drop it to match the proven-good local config. (Pair with re-storing GPG_PRIVATE_KEY from `gpg --export-secret-keys --armor` to rule out a mangled secret.) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Added a second commit: drop the optional |
Sync the docs with the workflow change in this PR: release.yml no longer reads ORG_GRADLE_PROJECT_signingInMemoryKeyId, so GPG_KEY_ID is no longer a secret the release consumes. Remove it from both "secrets to configure" tables. The key-creation/export narrative (finding the key id to run `gpg --export-secret-keys`) is unchanged — that's still required. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…ni PR #45) 1. :packages:core (com.convert:sdk-core) was still publishToMavenCentral() (manual) while :packages:sdk auto-released. Since sdk-android's POM depends on sdk-core, a split would publish sdk-android live against a still-staged sdk-core — a broken/partial release. Set core to automaticRelease = true so both modules publish together. 2. RELEASE.md "what the release does" steps were stale: removed the obsolete manual "click Publish" step (now auto-release), and corrected the @semantic-release/git commit-to-main + CHANGELOG description (qs-03 replaced it with @semantic-release/github tag + Release via API, no push to main). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1 participant
Per request: make the Maven Central publish auto-release instead of leaving a pending deployment for manual "Publish" in the Portal UI.
Change
packages/sdk/build.gradle.kts:publishToMavenCentral()→publishToMavenCentral(automaticRelease = true).Per the vanniktech docs, the no-arg form defaults to manual release (upload + validate, then click Publish in the Portal).
automaticRelease = truesets the deployment'spublishingType=AUTOMATICso it publishes to Maven Central automatically after validation. ("automaticRelease" is a publisher-side plugin setting — there is no equivalent toggle in the Central Portal UI.)Verified the build still configures (
./gradlew :packages:sdk:help).The latest Release run fails earlier, at GPG signing (
signMavenPublication > Could not read PGP secret key) — aGPG_PRIVATE_KEYsecret-content issue, separate from this change. This PR only changes what happens after a successful signed upload.🤖 Generated with Claude Code