chore: tidy up readme for now (#49)

.github/workflows/ci.yaml

@@ -51,23 +51,3 @@ jobs:
 
       - name: Run tests
         run: mvn test --file posthog/pom.xml --batch-mode --show-version
-
-      - name: Release to Maven Central
-        # Deploy the Java jar artifact to Maven Central using mvn deploy. If we
-        # are triggered by a release event, we use the release profile, and we
-        # set the version  the release version as the tag name. Otherwise, we
-        # set the version to the commit hash and append -SNAPSHOT to the
-        # version.
-        #
-        # This allows us to test the release process on branches without having
-        # to push a release.
-        run: |
-          if [[ $GITHUB_EVENT_NAME == release ]]; then
-            mvn deploy --file posthog/pom.xml --batch-mode --show-version -P release
-          else
-            mvn deploy --file posthog/pom.xml --batch-mode --show-version
-          fi
-        env:
-          GPG_PASSPHRASE: ${{ secrets.GPG_PASSPHRASE }}
-          MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }}
-          MAVEN_PASSWORD: ${{ secrets.OSSRH_PASSWORD }}

README.md

@@ -9,14 +9,6 @@ User guide available on
 We're using Sonatype OSSRH to host our open source project binaries. Docs:
 https://central.sonatype.org/publish/publish-guide/
 
-### Deploy via the CI
-
-Snapshot jars are release for all PR's, versioned with the short commit hash. To
-perform a production release, tag a commit with the version you want the jar to
-be published as.
-
-We authenticate with @hazzadous Sonatype credentials.
-
 ### Manual deployment
 
 #### 1. Get access to be able to deploy