Skip to content

fix: promote the staging repository to the Central Portal during CD - #23

Merged
RZEROSTERN merged 1 commit into
developfrom
bugfix/cd-portal-promotion
Oct 1, 2026
Merged

RZEROSTERN merged 1 commit into
developfrom
bugfix/cd-portal-promotion

Conversation

@RZEROSTERN

Copy link
Copy Markdown
Contributor

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

  • After the Gradle publish, the publish job now queries GET /manual/search/repositories?state=open and promotes every open repository with POST /manual/upload/repository/{key}?publishing_type=user_managed.
  • user_managed keeps the existing release gate: the deployment shows up in the Portal and a maintainer still presses Publish before anything goes public.
  • The job fails loudly if no open repository is found, instead of reporting a green run that shipped nothing.
  • The CI/CD docs (EN/ES/FR/PT) now describe the promotion step and the corrected flow diagram.

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:jacocoCoverageVerification passes locally (coverage gate ≥ 80%).
  • Workflow YAML validated; API contract verified against the Sonatype OSSRH Staging API documentation.

🤖 Generated with Claude Code

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>
@github-actions

github-actions Bot commented Oct 1, 2026

Copy link
Copy Markdown

Unit test coverage

Overall Project 83.51% 🍏

There is no coverage information present for the Files changed

@RZEROSTERN
RZEROSTERN merged commit 417d328 into develop Oct 1, 2026
2 checks passed
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