Remove unnecessary documentation sections from RELEASING.md

Co-authored-by: thomasturrell <1552612+thomasturrell@users.noreply.github.com>

Author: Copilot

RELEASING.md

@@ -100,34 +100,6 @@ Result:
   - Used for reproducible builds and deployments
 - **No separate release branches**: The release workflow pushes directly to the originating branch
 
-### CI Workflow Behavior
-
-**Important**: Release commits pushed by the automated workflow will **not** trigger other CI workflows (such as build or test workflows). This is because the workflow uses the default `GITHUB_TOKEN`, and GitHub intentionally prevents workflows from triggering other workflows to avoid infinite loops.
-
-- The release commits are still valid and properly signed by `github-actions[bot]`
-- Maven Central deployment happens within the release workflow itself
-- If you need CI to run on release commits, you would need to use a Personal Access Token (PAT) instead of `GITHUB_TOKEN`, though this is generally not recommended for releases
-
-## Version Numbering
-
-This project follows [Semantic Versioning](https://semver.org/):
-
-- **MAJOR** version (X): Incompatible API changes
-- **MINOR** version (Y): Backward-compatible functionality additions
-- **PATCH** version (Z): Backward-compatible bug fixes
-
-The automated workflow increments the **PATCH** version for the next development iteration.
-
-## Manual Override (Not Recommended)
-
-For special cases, you can still manually trigger the deprecated "Maven Release (Manual)" workflow:
-
-1. Go to [Actions](https://github.com/BerryCloud/xapi-java/actions)
-2. Select "Maven Release (Manual - Deprecated)"
-3. Click "Run workflow"
-
-**Note**: This method is deprecated and should only be used if the automated process fails.
-
 ## Troubleshooting
 
 ### Release Workflow Failed
@@ -195,25 +167,3 @@ If artifacts don't appear on Maven Central after a successful workflow:
 2. Deployment can take up to 2 hours to sync to Maven Central
 3. Check for any deployment errors in the workflow logs
 4. Verify GPG signing was successful (check for GPG-related errors)
-
-### CI Workflows Not Triggered by Release Commits
-
-**This is expected behavior**. Release commits pushed by the automated workflow will not trigger other CI workflows (such as build or test workflows). This is by design:
-
-- The workflow uses the default `GITHUB_TOKEN` for authentication
-- GitHub prevents workflows triggered by `GITHUB_TOKEN` from triggering other workflows to avoid infinite loops
-- The release workflow already performs all necessary building, testing, and deployment within itself
-- If you need CI workflows to run on release commits (generally not recommended), you would need to configure a Personal Access Token (PAT) instead
-
-## Required Secrets
-
-The following GitHub secrets must be configured for releases to work:
-
-- `OSSRH_USERNAME`: Sonatype OSSRH username
-- `OSSRH_TOKEN`: Sonatype OSSRH token
-- `MAVEN_GPG_PRIVATE_KEY`: GPG private key for signing artifacts
-- `MAVEN_GPG_PASSPHRASE`: Passphrase for the GPG private key
-
-## Snapshot Releases
-
-Snapshot versions are automatically published to Maven Central's snapshot repository when changes are pushed to `release-*` branches. See the "Publish snapshot to the Sonatype OSSRH" workflow.