Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automate Publication of Artifacts to the Central Repository #34

Closed
oliverspryn opened this issue Mar 28, 2024 · 1 comment · Fixed by #35
Closed

Automate Publication of Artifacts to the Central Repository #34

oliverspryn opened this issue Mar 28, 2024 · 1 comment · Fixed by #35
Assignees
Labels
Bug A defect which was discovered during development, testing, or while in production.
Milestone

Comments

@oliverspryn
Copy link
Owner

oliverspryn commented Mar 28, 2024

The CI cannot automatically publish and release the uploaded binaries to the Central Repository as-is. It can upload to OSSRH, but not automatically mark the binaries as ready for release to the Central Repository. To do so, it is missing this plugin: https://github.com/gradle-nexus/publish-plugin

Add this plugin and call the included closeAndReleaseSonatypeStagingRepository task during a publication build so that OSSRH can release the artifacts automatically.

See: gradle-nexus/publish-plugin#79

@oliverspryn oliverspryn added the Bug A defect which was discovered during development, testing, or while in production. label Mar 28, 2024
@oliverspryn oliverspryn added this to the 1.2.0 milestone Mar 28, 2024
@oliverspryn oliverspryn self-assigned this Mar 28, 2024
@oliverspryn
Copy link
Owner Author

Per: gradle-nexus/publish-plugin#236 this task is now closeAndReleaseStagingRepositories in v2 of the Nexus Publish Plugin, not closeAndReleaseSonatypeStagingRepository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug A defect which was discovered during development, testing, or while in production.
Projects
Development

Successfully merging a pull request may close this issue.

1 participant