Repository navigation
Publish Maven Central releases through the Publisher Portal API - #665
Draft
ramakrishnap-nv wants to merge 1 commit into
Draft
ramakrishnap-nv wants to merge 1 commit into
ramakrishnap-nv wants to merge 1 commit into
Conversation
The release path uploaded files one by one through the legacy ossrh-staging-api compatibility service and then handed the staging repository to the Portal. Sonatype asked projects to move to the Publisher API. Upload the signed bundle zip with POST /api/v1/publisher/upload as a USER_MANAGED deployment, then poll status as before. Publishing is still a manual step in the Portal UI. The staging profile id has no meaning in the Publisher API, so drop the profile-id input and option added in rapidsai#652. Rewrite the Maven Central integration test around the new flow. Its mock curl did not honor -o and -w, so the test already failed on main. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: Ramakrishna Prabhu <ramakrishnap@nvidia.com>
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.
Sonatype asked projects to move from the legacy
ossrh-staging-apito the Publisher API. This changes the Maven Central release path.POST /api/v1/publisher/uploadas aUSER_MANAGEDdeployment, then polled untilVALIDATED. Publishing is still a manual step in the Portal UI.profile-idinput and option from Decouple OSSRH staging profile from Maven groupId #652 are removed, since the Publisher API has no staging profile. cuOpt was the only caller using it.curldid not honor-oand-w, so it already failed onmain.The snapshot path already uses the Portal snapshot repository and is unchanged.
Tested with the integration test (upload, auto-drop on and off, upload failure,
FAILEDvalidation). Not yet run against the real Portal. This also changes cudf's release path, so it should be exercised on a real release before merging.Mirrors NVIDIA/cuopt#2195, which carries the same change in its vendored copy of this workflow.
🤖 Generated with Claude Code