docs: updated RELEASE.md

Author: quintesse

RELEASE.md

@@ -8,28 +8,40 @@ Releases are published to GitHub and Maven Central by JReleaser from a version t
 - Push access to the `codejive/java-properties` repository.
 - A Maven Central publisher account and namespace for `org.codejive`.
 - An armored GPG key configured in the repository's `jreleaser` environment:
-  `JRELEASER_GPG_PUBLIC_KEY`, `JRELEASER_GPG_SECRET_KEY`, and
-  `JRELEASER_GPG_PASSPHRASE`.
+    `GPG_PUBLIC_KEY`, `GPG_SECRET_KEY`, and `GPG_PASSPHRASE`.
 - The `MAVENCENTRAL_USERNAME` and `MAVENCENTRAL_PASSWORD` secrets.
 - The workflow-provided `GITHUB_TOKEN` permission to create releases.
 
-## Creating a Release
+## Creating a Release from GitHub.com
+
+1. Open [github.com/codejive/java-properties/actions](https://github.com/codejive/java-properties/actions).
+2. Select **Release** in the workflow list.
+3. Click **Run workflow**.
+4. Leave the branch set to `main` and enter the release version without a leading
+    `v`, for example `0.0.8`.
+5. Click **Run workflow** to start the release.
+6. Open the newly created workflow run and wait for the `release` job to complete.
+7. Open [github.com/codejive/java-properties/releases](https://github.com/codejive/java-properties/releases)
+    and verify the new GitHub release and its generated changelog.
+8. Verify that the component has been published to Maven Central.
+
+The workflow uses the `jreleaser` environment, so GitHub may pause the job until
+any required environment approval is granted.
+
+## Creating a Release from a Tag
 
 1. Ensure the changes are committed and the CI workflow is green.
 2. Create and push an annotated tag whose name is the release version, for example:
 
-	```shell
-	git tag -a v0.0.8 -m "Release v0.0.8"
-	git push origin v0.0.8
-	```
+    ```shell
+    git tag -a v0.0.8 -m "Release v0.0.8"
+    git push origin v0.0.8
+    ```
 
 3. The `Release` workflow sets the Maven version from the tag, builds the sources and
-	Javadoc artifacts, and runs JReleaser.
+    Javadoc artifacts, and runs JReleaser.
 4. Verify the GitHub release and the published component on Maven Central.
 
-The workflow can also be started manually from GitHub Actions. In that case, provide
-the version without the leading `v`.
-
 ## Local Configuration Check
 
 This validates the JReleaser configuration without publishing anything:
@@ -49,20 +61,7 @@ signing keys remain outside the local environment.
 
 ## Recovery
 
-```
-./mvnw jreleaser:full-release
-```
-
-Re-running the workflow for the same tag is safe because the JReleaser GitHub release
-configuration allows overwriting an existing release. If a release must be corrected,
-fix the source, create a new patch version, and push a new tag.
-
-```
-mvn -B release:update-versions -DdevelopmentVersion=1.2.3-SNAPSHOT
-```
-
-A manual deploy can be done like this:
-
-```
-mvn clean deploy -P release
-```
+If a workflow fails, open its run in **Actions**, inspect the failed step, correct the
+underlying issue, and use **Re-run failed jobs**. If the release must be corrected
+after publication, fix the source, choose a new patch version, and run the workflow
+again from GitHub.com.