Configure Gitea Actions release workflow to compile and publish standalone binaries via runner

README.md

@@ -266,22 +266,24 @@ This tests invalid token rejection, encrypted socket streaming, database persist
 
 ---
 
-## Publishing Releases (Direct Binary Upload to Gitea)
+## Automated Releases via Gitea Actions
 
-Since Gitea does not have active action runners, you can compile and upload releases directly from your workstation using [`upload_release.py`](upload_release.py):
+Releases are automated via [`.gitea/workflows/release.yml`](.gitea/workflows/release.yml) using your Gitea action runner:
 
-### One-Command Release Publishing
+### Publishing a Release
+Whenever you want to release a new version with compiled standalone binaries:
 ```bash
-python upload_release.py --tag v1.0.0 --token <YOUR_GITEA_TOKEN>
+git tag v1.0.0
+git push origin v1.0.0
 ```
-*(Or set `set GITEA_TOKEN=...` in your terminal and simply run `python upload_release.py --tag v1.0.0`)*
 
-### What It Does:
-1. Calls `package_dist.py` to compile native binaries:
-   - `Win_Client.exe`
-   - `Server.exe`
-   - `Linux_Client.bin`
-   - `SHA256SUMS.txt`
-2. Connects to `https://gitea.eibl.tech/api/v1/repos/me0nline/LOGAR`.
-3. Creates the Gitea release for `v1.0.0` (or updates an existing release).
-4. Uploads only the compiled binary assets as downloadable attachments.
+### What Gitea Actions Does Automatically:
+1. Gitea runner executes the workflow on tag push.
+2. Runs `package_dist.py` to compile native standalone binaries:
+   - `Linux_Client.bin` (standalone binary)
+   - `Server.bin` (standalone server binary)
+   - `Win_Client.pyz` (standalone executable zipapp)
+   - `SHA256SUMS.txt` (checksums)
+3. Publishes the Gitea release using `gitea-release-action` and attaches the compiled binary assets.
+
+*(Note: You can also use `upload_release.py` from your Windows machine to upload Windows `.exe` binaries directly if desired).*