Use versioned app releases for binary package
All checks were successful
Release App / release-app (push) Successful in 1m31s

This commit is contained in:
2026-04-24 15:00:42 +03:00
parent 5a5677a994
commit 891fc73e25
3 changed files with 29 additions and 13 deletions

View File

@@ -69,9 +69,9 @@ It also refreshes a `latest/tdlib-latest.json` manifest with the newest publishe
The repository also includes [`.gitea/workflows/release-app.yaml`](.gitea/workflows/release-app.yaml),
which downloads a prebuilt TDLib bundle from the `shinoa-tdlib` repository using a pinned
version tag such as `v1.8.63`, builds a
rolling `latest` app release, and publishes an archive containing `usr/bin/shinoa` plus the
versioned app release tag such as `v0.1.0`, and publishes an archive containing `usr/bin/shinoa` plus the
bundled `usr/lib/libtdjson.so*`. The root `PKGBUILD` installs that prebuilt release as
`shinoa-bin`. That workflow expects Gitea secrets named `TELEGRAM_API_ID` and
`shinoa-bin`. The package disables debug splitting with `options=(!debug)`. That workflow expects Gitea secrets named `TELEGRAM_API_ID` and
`TELEGRAM_API_HASH`. Release builds are configured to fail if those secrets are missing.
To prepare the TDLib bundle on your own machine: