Adding container registry login for gitea action

docs/publish.md

@@ -296,9 +296,10 @@ line in `.gitea/workflows/release.yml` to the versioned tag instead.
    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`.
+
+   No manual `docker login` needed on the runner host — the workflow's
+   `container:` block authenticates the image pull itself via the
+   `REGISTRY_USER`/`REGISTRY_PASSWORD` secrets (§4.3).
 
 ### 4.3 Repo secrets
 
@@ -308,6 +309,8 @@ Settings → Actions → Secrets, add:
 |---|---|
 | `RELEASE_KEYSTORE_B64` | `base64 -w0 SchwertUndMagieOnPebbleCompanionApp/release.keystore` |
 | `RELEASE_KEYSTORE_PROPERTIES` | the full contents of `SchwertUndMagieOnPebbleCompanionApp/keystore.properties` (§2.2) |
+| `REGISTRY_USER` | same as `REGISTRY_USER` in `registry.env` |
+| `REGISTRY_PASSWORD` | same as `REGISTRY_PASSWORD` in `registry.env` |
 
 `secrets.GITEA_TOKEN` (used to create the release and upload assets) is
 Gitea's own auto-generated per-job token — nothing to create or add yourself.