Is it possible to configure a Maven Sonatype Nexus such that only a subset of maintainers can promote artifacts to Maven Central?

My team publishes multiple open-source packages. We use Sonatype Nexus as our "staging" repository, do QA on the packages, and then manually "close and release" the repository, promoting the packages to Maven Central. Basically everyone in the team can perform any of these actions. I'd like to know if it's possible to configure our Nexus instance such that: everyone can keep doing everything they can currently do (create/delete repositories, add packages to them, etc)... except that only a subset of users can "release" the repository. I've taken a look at Nexus Privileges and they seem promising, but the documentation isn't particularly clear on the particular point of promoting to Maven Central (since the docs are ecosystem-agnostic). So, specifically, which privilege controls the ability to promote artifacts to Maven Central? nexus:repository-admin:maven2:*:edit? What other permissions are set by this privilege (i.e. what other things will users no longer be able to do)? (I'm not an admin, so I can't test things out myself...)

Jan 17, 2025 - 18:05
Is it possible to configure a Maven Sonatype Nexus such that only a subset of maintainers can promote artifacts to Maven Central?

My team publishes multiple open-source packages. We use Sonatype Nexus as our "staging" repository, do QA on the packages, and then manually "close and release" the repository, promoting the packages to Maven Central. Basically everyone in the team can perform any of these actions.

I'd like to know if it's possible to configure our Nexus instance such that:

  • everyone can keep doing everything they can currently do (create/delete repositories, add packages to them, etc)...
  • except that only a subset of users can "release" the repository.

I've taken a look at Nexus Privileges and they seem promising, but the documentation isn't particularly clear on the particular point of promoting to Maven Central (since the docs are ecosystem-agnostic).

So, specifically, which privilege controls the ability to promote artifacts to Maven Central? nexus:repository-admin:maven2:*:edit? What other permissions are set by this privilege (i.e. what other things will users no longer be able to do)?

(I'm not an admin, so I can't test things out myself...)