Releasing Deployment from OSSRH to the Central Repository - Introduction⚓︎

After a successful deployment to OSSRH your components are stored in aseparate, temporary repository, that is private to your projects members. Inorder to get these components published you will have to 'release' them. If youfind any issues upon examination in the repository, you can alsoDrop thestaging repository. This allows you to re-run the deployments after fixing anyissues found and avoids the publication of these components into the releaserepository and sub-sequentially into the Central Repository.

Typically, this process is done manually, but it is also possible to trigger theactions from the command line.

Login into OSSRH⚓︎

You need to log in to OSSRH available athttps://s01.oss.sonatype.org/ in order to access andwork with your staging repositories.

Note: As of February 2021, all new projects began being provisioned onhttps://s01.oss.sonatype.org/. If your project was provisioned before this date,please log in to the legacy hosthttps://oss.sonatype.org/.

Locate and Examine Your Staging Repository⚓︎

Once you are logged in you will be able to access the Build Promotion menu inthe left hand navigation and select the Staging Repositories item. The StagingRepositories tab with a long list of repositories will be displayed.

The staging repository you created during the deployment will have a namestarting with the groupId for your projects with the dots removed appended witha dash and a 4-digit number. E.g. if your project groupId iscom.example.applications, your staging profile name would start withcomexampleapplications. The sequential numbers start at 1000 and are incrementedper deployment, so you could e.g. have a staging repository name ofcomexampleapplication-1010.

Select the staging repository and the panel below the list will display furtherdetails about the repository. In addition, the buttonsClose andRelease willbe activated.

Close and Drop or Release Your Staging Repository⚓︎

After your deployment the repository will be in anOpen status. You canevaluate the deployed components in the repository using theContents tab. Ifyou believe everything is correct you, can press theClose button above thelist. This will trigger the evaluations of the components against therequirements.

Closing will fail if your components do not meet the requirements. If thishappens, you can pressDrop and the staging repository will be deleted. Thisallows you to correct any problems with the components and the deploymentprocess and re-run the deployment. Details are available in theActivity tabbelow the list by selecting. Press on the individual steps for further details.

Once you have successfully closed the staging repository, you can release it bypressing theRelease button. This will move the components into the releaserepository of OSSRH where it will be synced to the Central Repository.

Note that deploying with the Nexus Staging Maven plugin or Ant tasks will, bydefault, automatically attempt to close the staging repository upon deploymentand can be used to release the staging repository from the command line as well.This allows you to avoid logging into the OSSRH user interface altogether. Moredetails can be found in theMaven andAnt sections of this guide.