Skip to content

Commit 004bdbd

Browse files
dfa1claude
andcommitted
build: add maven-release-plugin for tagging releases
Mirror vortex-java: release:prepare drops -SNAPSHOT, tags v<version> (pushChanges=false, autoVersionSubmodules), bumps to next snapshot. Pushing the v* tag triggers publish.yml -> deploy -Prelease to Maven Central. Document the flow in the release profile comment. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1 parent 2bcdf32 commit 004bdbd

1 file changed

Lines changed: 10 additions & 5 deletions

File tree

pom.xml

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -211,13 +211,18 @@
211211
</build>
212212

213213
<profiles>
214-
<!-- Release to Maven Central: ./mvnw deploy -Prelease
214+
<!-- Cut a release with maven-release-plugin (configured in build above):
215+
./mvnw release:prepare
216+
drops -SNAPSHOT, commits, tags v<version> (pushChanges=false), then
217+
bumps to the next snapshot. Push the commits and the tag; the v* tag
218+
triggers .github/workflows/publish.yml, which runs
219+
./mvnw deploy -Prelease
220+
to sign and upload to Maven Central.
215221
Prerequisites:
216222
1. Register namespace io.github.dfa1 at central.sonatype.com.
217-
2. Generate a user token (Account / User Tokens) and add it to
218-
~/.m2/settings.xml as a server with id "central".
219-
3. A published GPG key.
220-
CI does this on a v* tag via .github/workflows/publish.yml. -->
223+
2. A Central user token (Account / User Tokens); in CI it comes from
224+
the CENTRAL_USERNAME / CENTRAL_PASSWORD secrets.
225+
3. A published GPG key (GPG_PRIVATE_KEY / GPG_PASSPHRASE secrets). -->
221226
<profile>
222227
<id>release</id>
223228
<build>

0 commit comments

Comments
 (0)