From e0e5c87ce9a57b3c55ae81acbe064b6894d1c66f Mon Sep 17 00:00:00 2001 From: Sylwester Lachiewicz Date: Sat, 8 Aug 2026 19:42:14 +0200 Subject: [PATCH] Correct the release procedure: publishing is automatic, not manual RELEASING.md said release:perform stages to the Central Portal and the release manager then publishes from the Portal UI. That is wrong. maven-release-plugin runs with releaseProfiles=plexus-release, which sets njord.enabled=true. Njord is registered as a build extension and configured with autoPublish=true and publishingType=automatic, so it publishes the deployment itself. Also records that releasing needs Maven 3.9.0, since the plexus-release profile raises minimalMavenBuildVersion above the 3.6.3 an ordinary build requires. --- RELEASING.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/RELEASING.md b/RELEASING.md index 42f28d8..20621e5 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -31,7 +31,13 @@ mvn release:prepare mvn release:perform ``` -`release:prepare` tags and bumps versions; `release:perform` builds from the tag and stages to the Central Portal. Then publish the staged deployment from the Central Portal UI. +`release:prepare` tags and bumps versions; `release:perform` builds from the tag and deploys. + +There is no manual publish step. `maven-release-plugin` is configured in the parent with `deploy` and `plexus-release`, so `release:perform` activates the `plexus-release` profile. That profile adds GPG signing, attaches sources and a source-release assembly, and sets `njord.enabled=true`. + +[Njord](https://maveniverse.eu/docs/njord/) is registered as a build extension and configured with `autoPublish=true` and `publishingType=automatic`, so it publishes the deployment to Central itself. `njord.enabled` is `false` outside the release profile, so ordinary builds are unaffected. + +Releasing needs Maven **3.9.0** or later — the `plexus-release` profile raises `minimalMavenBuildVersion` above the 3.6.3 required for a normal build. Afterwards: