actions: registry token
Build and Publish Container / Publish Linux container (push) Successful in 6m24s

This commit is contained in:
2026-10-02 13:02:06 -04:00
parent 7ac541def5
commit fa6eb856dc
2 changed files with 22 additions and 5 deletions
+9 -3
View File
@@ -72,9 +72,15 @@ git.hudsonriggs.systems/hriggs/progressionmods:latest
```
Published tags include `latest`, the branch or semantic version, and
`sha-<commit>`. The workflow uses the Gitea action token by default. If the
server does not grant that token package-write access, configure repository
secrets named `REGISTRY_USERNAME` and `REGISTRY_TOKEN`.
`sha-<commit>`. Before running the workflow, configure `REGISTRY_TOKEN` as a
repository Actions secret containing a Gitea personal access token with
`write:package` permission.
The registry username defaults to `HRiggs`. An optional `REGISTRY_USERNAME`
secret can override it.
Gitea's built-in Actions token cannot currently publish OCI packages, so the
registry token is required even though the workflow requests `packages: write`.
### Mod-list endpoints