feat: Migrate from OSSRH to Maven Central Publishing API#68
feat: Migrate from OSSRH to Maven Central Publishing API#68jmadhur87 wants to merge 3 commits intofortify:masterfrom
Conversation
.github/workflows/ci.yml
Outdated
| - name: Publish to Maven Central | ||
| if: github.ref == 'refs/heads/master' | ||
| run: ./gradlew publishToOSSRH closeOSSRHStagingRepository | ||
| run: ./gradlew publishToSonatype closeAndReleaseSonatypeStagingRepository |
There was a problem hiding this comment.
@jmadhur87 Unless it's somehow required by Gradle plugins, I think it would be more clear to have publishToMavenCentral instead of publishToSonatype Gradle task, and repository mavenCentral instead of sonatype in nexusPublishing section. Other than that, I'm OK with the changes assuming you've tested these, so please go ahead and merge once you've updated sonatype to mavenCentral as described above.
SangameshV
left a comment
SangameshV
left a comment
There was a problem hiding this comment.
Hi @jmadhur87 , please handle this review point.
| - name: Publish to Maven Central | ||
| if: github.ref == 'refs/heads/master' | ||
| run: ./gradlew publishToSonatype closeAndReleaseSonatypeStagingRepository | ||
| run: ./gradlew publishToMavenCentral closeAndReleaseSonatypeStagingRepository |
There was a problem hiding this comment.
Since the repository name in build.gradle was changed from sonatype to mavenCentral, the io.github.gradle-nexus.publish-plugin now creates the task closeAndReleaseMavenCentralStagingRepository. Please update the configuration to use this task name.
2 participants
Bump client version from 25.2 -> 25.4
Updated Publishing configuration to publish to Sonatype/Maven Central
Updated CI workflow