dist.sh builds versioned, signed artifacts for both apps from a git tag

(semver drives Android versionCode/versionName and package.json). The
build-image/ Dockerfile pins the same toolchain for a portable,
containerized Gitea Actions runner (build-image.sh builds and pushes
it) so releases don't depend on any one machine's local setup.
Pushing vX.Y.Z now builds and publishes a Gitea Release automatically.

.gitea/workflows/release.yml

@@ -13,8 +13,10 @@ jobs:
     # regardless of this instance's default Actions permission mode.
     permissions:
       contents: write
-    # Must match the label your self-hosted act_runner registers with.
-    runs-on: self-hosted
+    # Must match a label your act_runner is registered with. The runner's
+    # own default label-image is irrelevant here since `container:` below
+    # overrides the actual build image per-job.
+    runs-on: ubuntu-latest
     container:
       # :latest — always the most recently pushed build-image.sh output.
       # Pin to a specific tag here (see build-image/VERSION) if you need a

docs/publish.md

@@ -285,15 +285,17 @@ line in `.gitea/workflows/release.yml` to the versioned tag instead.
    # https://gitea.com/gitea/act_runner — grab the latest release binary
    ./act_runner register --no-interactive \
      --instance <your gitea URL> --token <token> \
-     --name <runner-name> --labels self-hosted:docker://node:20-bookworm
+     --name <runner-name> --labels ubuntu-latest:docker://node:20-bookworm
    ./act_runner daemon
    ```
    The image after `docker://` in `--labels` is only a fallback for jobs that
    don't specify their own `container:` — irrelevant here since
    `.gitea/workflows/release.yml` always pins its own image, but the runner
    still needs a Docker-executor label registered to use that executor at
-   all. The label name itself (`self-hosted`) must match `runs-on:` in
-   `.gitea/workflows/release.yml` — edit both together if you rename it.
+   all. The label name itself (`ubuntu-latest` above) must match `runs-on:`
+   in `.gitea/workflows/release.yml` — edit both together if you rename it,
+   or reuse a label an existing runner already advertises (check Site Admin →
+   Actions → Runners) to skip registering a new one entirely.
 4. The runner's Docker daemon needs pull access to the registry — run
    `docker login <registry>` once on that machine with the same credentials
    as `registry.env`.