Remove Sonatype supoporting

README.md

@@ -79,39 +79,6 @@ plugins {
 }
 ```
 
-<details>
-<summary>Snapshot builds are also available</summary>
-___
-
-You'll need to add the Sonatype snapshots repository.
-Look for the actual version of the snapshot in the name of the opened `snapshot-<VERSION>` repository branch.
-
-For general integration add next snippet in `./settings.gradle`
-
-```kotlin
-pluginManagement {
-
-  resolutionStrategy {
-    eachPlugin {
-      if(requested.id.namespace == "ru.cian") {
-        useModule("ru.cian.rustore-plugin:rustore-publish-gradle-plugin:<SNAPSHOT-VERSION>")
-      }
-    }
-  }
-
-  plugins {
-    id("ru.cian.rustore-publish-gradle-plugin") version rustorePublish apply false
-  }
-
-  repositories {
-    maven { url 'https://oss.sonatype.org/content/repositories/snapshots' }
-  }
-}
-```
-___
-
-</details>
-
 ## Using the `apply` method
 
 ```groovy
@@ -129,31 +96,6 @@ apply plugin: 'com.android.application'
 apply plugin: 'ru.cian.rustore-publish-gradle-plugin'
 ```
 
-<details>
-<summary>Snapshot builds are also available</summary>
-___
-
-You'll need to add the Sonatype snapshots repository.
-Look for the actual version of the snapshot in the name of the opened `snapshot-<VERSION>` repository branch.
-
-```groovy
-buildscript {
-    repositories {
-        maven { url 'https://oss.sonatype.org/content/repositories/snapshots' }
-    }
-
-    dependencies {
-        classpath "ru.cian.rustore-plugin:rustore-publish-gradle-plugin:<VERSION>-SNAPSHOT"
-    }
-}
-
-apply plugin: 'com.android.application'
-apply plugin: "ru.cian.rustore-publish-gradle-plugin"
-```
-___
-
-</details>
-
 ## Quickstart Plugin Configuration
 
 ```kotlin

RELEASING.md

@@ -1,27 +1,18 @@
 How To Release
 ==============
 
-Due to Maven Central's very particular requirements, the release process is a bit
-elaborate and requires a good deal of local configuration.  This guide should walk
-you through it.  It won't do anyone outside of KeepSafe any good, but the workflow
-is representative of just about any project deploying via Sonatype.
-
-We currently deploy to both Maven Central (via Sonatype's OSS Nexus instance) and to
-plugins.gradle.org.
+We currently deploy the plugin only to the Gradle Portal plugins.gradle.org.
 
 ## Prerequisites
 
 1. A *published* GPG code-signing key
-1. A Sonatype Nexus OSS account with permission to publish in ru.cian
 1. A plugins.gradle.org account with permission to publish in ru.cian
 1. Permission to push directly to https://github.com/cianru/rustore-publish-gradle-plugin
 
 ## Contents page
 
 1. [Setup](docs/releasing/01-setup.md)
-2. [Pushing a SNAPSHOT build to local repository](docs/releasing/02-publish-a-snapshot-to-local-repository.md)
-3. [Pushing a SNAPSHOT build to Sonatype](docs/releasing/03-publish-a-snapshot-to-sonatype.md)
-4. [Pushing a release build to Sonatype](docs/releasing/04-publish-a-release-build-to-sonatype.md)
+2. [Pushing a build to local repository](docs/releasing/02-publish-a-build-to-local-repository)
 5. [Pushing a release build to Gradle Plugin Portal](docs/releasing/06-publish-a-release-build-to-gradle-plugin-portal.md)
 6. [Prepare Release Commit](docs/releasing/07-prepare-release-commit.md)
-7. [Prepare Next Snapshot Version Commit](docs/releasing/08-prepare-next-snapshot-version-commit.md)
+7. [Prepare Next Alpha Version Commit](docs/releasing/08-prepare-alpha-version-commit)

docs/releasing/01-setup.md

@@ -2,17 +2,6 @@
 
 1. Add your GPG key to your github profile - this is required
    for github to know that your commits and tags are "verified".
-1. Configure your code-signing key in ~/.gradle.properties:
-   ```gradle
-   signing.keyId=<key ID of your GPG signing key>
-   signing.password=<your key's passphrase>
-   signing.secretKeyRingFile=/path/to/your/secring.gpg
-   ```
-1. Configure your Sonatype credentials in ~/.gradle/gradle.properties:
-   ```gradle
-   SONATYPE_NEXUS_USERNAME=<nexus username>
-   SONATYPE_NEXUS_PASSWORD=<nexus password>
-   ```
 1. Configure git with your codesigning key; make sure it's the same as the one
    you use to sign binaries (i.e. it's the same one you adaded to gradle.properties):
    ```bash

docs/releasing/02-publish-a-snapshot-to-local-repository.md → docs/releasing/02-publish-a-build-to-local-repository.md

@@ -4,15 +4,11 @@
     ```
     cd ./plugin
     ```
-2. Edit the `gradle.properties` file:
-   ```bash
-   IS_SNAPSHOT=true
-   ```
-3. Publish to local repository
+2. Publish to local repository
    ```bash
    ./gradlew :plugin:publishToMavenLocal
    ```
-4. Remove local repository to apply remote build repository
+3. Remove local repository to apply remote build repository
    ```bash
    rm -rv ~/.m2/repository/ru/cian/rustore-publish-gradle-plugin/
    ```

docs/releasing/06-publish-a-release-build-to-gradle-plugin-portal.md

@@ -5,9 +5,7 @@
     cd ./plugin
     ```
 1. Edit the `gradle.properties` file:
-   ```bash
-   IS_SNAPSHOT=false
-   ```
+   Remove `-alpha<number>` from the `VERSION_NAME` and set the version to the release version. For example: `1.0.0`.
 1. Verify that the everything works:
    ```bash
    ./gradlew clean check

docs/releasing/08-prepare-alpha-version-commit.md

@@ -0,0 +1,12 @@
+## Prepare Next Snapshot Version Commit
+
+1. Create new `alpha-<version>` Git branch
+2. Open the plugin directory:
+    ```
+    cd ./plugin
+    ```
+3. Edit the `gradle.properties` file to set new `VERSION_NAME`+ `-alpha<number>` version. For example: `1.0.0-alpha01`.
+4. Make a *signed* commit:
+   ```bash
+   git commit -m "Prepare next development version"
+   ```

gradle/libs.versions.toml

@@ -13,7 +13,7 @@ kotlin = "1.9.23"
 detekt = "1.23.4"
 junitJupiter = "5.9.3"
 androidGradlePlugin = "8.0.2"
-sampleRustorePlugin = "0.5.0-SNAPSHOT"
+sampleRustorePlugin = "0.5.0-alpha02"
 
 [libraries]
 appcompat = "androidx.appcompat:appcompat:1.6.1"

plugin/build.gradle.kts

@@ -8,7 +8,6 @@ plugins {
     alias(libs.plugins.kotlinJvm)
 }
 
-apply(from = "$projectDir/config/maven-publish.gradle")
 apply(from = "$projectDir/config/gradle-portal.gradle")
 
 detekt {