ci: use DEPLOY_TOKEN secret (GITEA_ prefix is reserved)
Gitea forbids secret names starting with GITEA_; map the DEPLOY_TOKEN secret to the GITEA_TOKEN env var consumed by publish.sh.
This commit is contained in:
+3
-2
@@ -49,8 +49,9 @@
|
||||
|
||||
## Integration points
|
||||
|
||||
- **Gitea Actions** reads `secrets.GITEA_TOKEN` (scope `write:package`) and
|
||||
`GITEA_OWNER`/`GITEA_URL`; publish job runs only on `main`.
|
||||
- **Gitea Actions** reads the `DEPLOY_TOKEN` secret (scope `write:package`) and
|
||||
`GITEA_OWNER`/`GITEA_URL`; publish job runs only on `main`. Secret names must not start with
|
||||
the reserved `GITEA_` prefix.
|
||||
- **`scripts/publish.sh`** uploads via `curl` to the generic registry; package names are
|
||||
prefixed `rule-*` and `gate-*`.
|
||||
- **Consumer contract**: bundles scope roots to `rules` so operators can supply
|
||||
|
||||
Reference in New Issue
Block a user