ci: use DEPLOY_TOKEN secret (GITEA_ prefix is reserved)
ci / verify (push) Successful in 4m3s
ci / publish (push) Failing after 47s

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:
jdevega
2026-09-15 20:34:56 +02:00
parent cc8e9a23b3
commit 953523e40a
5 changed files with 13 additions and 7 deletions
+2 -1
View File
@@ -35,4 +35,5 @@ Bundles are built from `package.json#version`, so the registry upload uses the n
CI verifies (format, lint, schema check, tests) and builds bundles on every push/PR. On `main`
the `publish` job uploads the bundles to the Gitea generic package registry using the
`GITEA_TOKEN` repository secret (requires `write:package` scope).
`DEPLOY_TOKEN` repository secret (requires `write:package` scope). Secret names cannot start
with the reserved `GITEA_` prefix.