fix: update Gitea token reference in documentation and workflows to use RELEASE_TOKEN
tests / python (3.10) (push) Successful in 14s
tests-macos / macos (push) Successful in 17s
tests / python (3.11) (push) Successful in 13s
tests / web (push) Successful in 38s
release / release (push) Successful in 36s

This commit is contained in:
Netherwarlord
2026-07-29 14:58:15 -04:00
parent 4a0501c9fb
commit 7bfec91a47
4 changed files with 37 additions and 7 deletions
+1 -1
View File
@@ -502,7 +502,7 @@ git tag v2.0.0 && git push origin v2.0.0
The Gitea one needs only a single runner because the cross-build makes the
archives independent of build host — see
[packaging/GITEA-SETUP.md](packaging/GITEA-SETUP.md) for runner registration and
the `GITEA_TOKEN` secret. `publish_gitea.py` is stdlib-only and idempotent:
the `RELEASE_TOKEN` secret. `publish_gitea.py` is stdlib-only and idempotent:
re-running on the same tag replaces assets rather than duplicating them.
---