Repository navigation
Release: CD portal promotion fix for Maven Central publishing - #24
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>
fix: promote the staging repository to the Central Portal during CD
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.
Summary
Brings the Central Portal promotion fix (#23) into
masterso release runs actually surface a deployment to publish.What changed
.github/workflows/cd.yml): after the signed Gradle upload, the publish job now queries the OSSRH staging API for open staging repositories and promotes each one to the Central Portal (publishing_type=user_managed). Previously the upload stayed in an open staging repository the Portal never displays, which is why the green v1.0.0 run published nothing. The job fails loudly if there is nothing to promote.docs/{en,es,fr,pt}/ci.md): the continuous-deployment section and its flow diagram now describe the promotion step.The Portal Publish button remains the final release gate — nothing goes public automatically.
After merging
master). It re-uploads the 1.0.0 artifacts and promotes the staging repository, making the deployment visible in the Portal. No new tag is needed;VERSION_NAMEis still 1.0.0.Testing
./gradlew testDebugUnitTest :openpay-sdk:jacocoCoverageVerificationpasses (coverage gate ≥ 80%).🤖 Generated with Claude Code