lyuksovannyy 965fb5a284 Read the release token from RELEASE_TOKEN ...

The publish step set GITEA_TOKEN from the org-level API_TOKEN secret, but
the Actions runner injects its own GITEA_TOKEN into every step and that
value overrides a step-level env: entry of the same name. The org secret
was silently ignored and the job failed.

Pass the secret as RELEASE_TOKEN instead, which the runner does not
reserve, and read that name in release.py. --token-env makes the source
configurable, so the runner-provided GITEA_TOKEN can still be used
deliberately by passing --token-env GITEA_TOKEN.

2026-09-13 00:10:07 +02:00

..

workflows

Read the release token from RELEASE_TOKEN

2026-09-13 00:10:07 +02:00