me0nline/LOGAR
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 4 Wiki Activity

docs: update release tag instructions for v2.0.1 in root README.md
CI Test Suite / Run Component Tests & Pipeline Verification (push) Successful in 2m15s
Details

Browse Source
This commit is contained in:
me0nline
2026-09-04 23:31:44 +02:00
parent 956dfc5d93
commit fd6da560ed
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+4 -4
View File
@@ -372,8 +372,8 @@ Releases can be built and published through three complementary channels:
### 1. Tag Push Automation (Gitea Actions) ### 1. Tag Push Automation (Gitea Actions)
Pushing a release tag automatically triggers the build workflows: Pushing a release tag automatically triggers the build workflows:
```bash ```bash
git tag v2.0.0 git tag v2.0.1
git push origin v2.0.0 git push origin v2.0.1
``` ```
The consolidated workflow **`release.yml`** defines two parallel jobs: The consolidated workflow **`release.yml`** defines two parallel jobs:
- **`release-linux`** (`ubuntu-latest`): Compiles standalone native ELF binaries (`Linux_Client.bin`, `Server.bin`) and checksums. - **`release-linux`** (`ubuntu-latest`): Compiles standalone native ELF binaries (`Linux_Client.bin`, `Server.bin`) and checksums.
@@ -382,7 +382,7 @@ The consolidated workflow **`release.yml`** defines two parallel jobs:
### 2. Manual Workflow Dispatch (Gitea UI) ### 2. Manual Workflow Dispatch (Gitea UI)
Workflows can be manually triggered on demand from the Gitea web interface: Workflows can be manually triggered on demand from the Gitea web interface:
1. Navigate to **Actions** $\rightarrow$ **Release Binaries & Installers** (`release.yml`). 1. Navigate to **Actions** $\rightarrow$ **Release Binaries & Installers** (`release.yml`).
2. Click **Run workflow**, set the release tag (defaults to `v2.0.0`), and run. 2. Click **Run workflow**, set the release tag (defaults to `v2.0.1`), and run.
### 3. Native Local Windows Build & Direct Release Upload ### 3. Native Local Windows Build & Direct Release Upload
For environments without a registered Windows CI runner, Windows executables can be built and published directly to Gitea releases: For environments without a registered Windows CI runner, Windows executables can be built and published directly to Gitea releases:
@@ -391,5 +391,5 @@ For environments without a registered Windows CI runner, Windows executables can
python compilation/package_dist.py --target windows python compilation/package_dist.py --target windows
# 2. Upload assets and release notes directly to the Gitea release # 2. Upload assets and release notes directly to the Gitea release
python compilation/upload_release.py --tag v2.0.0 --token <GITEA_TOKEN> --skip-build python compilation/upload_release.py --tag v2.0.1 --token <GITEA_TOKEN> --skip-build
``` ```