Repository navigation
fix: promote the staging repository to the Central Portal during CD - #23
Merged
Merged
Conversation
The Gradle upload to the OSSRH staging API lands in an open staging repository that never appears in the Central Portal, so there was nothing to publish after a release run. The publish job now calls the staging API's manual endpoint to promote every open repository as a user-managed deployment, keeping the final Publish button as the release gate. The CI docs in all four languages describe the new step. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Unit test coverage
|
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
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.
Problem
The v1.0.0 CD run (#36826464339) finished green, but nothing reached Maven Central and no deployment ever appeared under Publish → Deployments in the Central Portal.
The cause: the Gradle upload goes to the OSSRH staging API compatibility endpoint (
/service/local/staging/deploy/maven2/), which keeps the artifacts in an open staging repository. That repository is invisible in the Portal until it is promoted through the staging API's manual endpoint — a step the workflow never performed, so the release was stranded with no Publish button to press.Fix
publishjob now queriesGET /manual/search/repositories?state=openand promotes every open repository withPOST /manual/upload/repository/{key}?publishing_type=user_managed.user_managedkeeps the existing release gate: the deployment shows up in the Portal and a maintainer still presses Publish before anything goes public.Rescuing v1.0.0
After this merges, re-run the CD workflow via Run workflow (workflow_dispatch) — it re-uploads the 1.0.0 artifacts into the open staging repository and promotes it, making the deployment visible in the Portal for the final Publish.
Testing
./gradlew testDebugUnitTest :openpay-sdk:jacocoCoverageVerificationpasses locally (coverage gate ≥ 80%).🤖 Generated with Claude Code