From 8597eae7049c7a148246b6f5d61b0032810a8f9f Mon Sep 17 00:00:00 2001 From: Geoff Powell Date: Thu, 9 Jan 2025 10:13:09 -0500 Subject: [PATCH] Add docs for internal releases --- RELEASING.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/RELEASING.md b/RELEASING.md index e3a156e624..f782d894a5 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -14,3 +14,13 @@ 8. `git push && git push --tags` This will trigger a GitHub Action workflow which will create a GitHub release and upload the release artifacts to Maven Central. + +## Internal Releasing + +1. Update `VERSION_NAME` in `gradle.properties` to the internal release (non-SNAPSHOT) version. [2.0.0-internal01] Ensure that the name doesn't collide with an already released version. +2. Update `RELEASE_SIGNING_ENABLED` in `gradle.properties` to `false`. +3. Check that the internal variables are configured correctly: + 1. `internalUrl` is set in `~/.gradle/gradle.properties` to the internal repository URL. + 2. Check `internalUsername` and `internalPassword` are set in `~/.gradle/gradle.properties` to the internal repository credentials. +4. Run `./gradlew publishMavenPublicationToInternalRepository paparazzi-gradle-plugin:publishAllPublicationsToInternalRepository --no-parallel` to publish the internal release. + * *Note* if gradle publish fails with `403` error, ensure the `VERSION_NAME` in step 1 is unique and isn't already published.