Paul Schneider 0759bae1a3 purge GITHUB_TOKEN / GITHUB_ENV naming, switch to forgejo.token ... Following up on the previous commit (forgejo.* / FORGEJO_TOKEN env vars): the previous version still had two carve-outs that kept github-flavoured names alive in this script, namely - ${{ secrets.GITHUB_TOKEN }} (token source) -> ${{ forgejo.token }} - $GITHUB_ENV (inter-step state file) -> /tmp/release-state.env Both name choices were inherited from yavsc's workflow without re-checking. Neither is forced by Forgejo; the auto-provided token is exposed via the forgejo context, and inter-step state can be persisted via a plain env file sourced at the top of each step. Result: zero occurrences of 'github' (case-insensitive) anywhere in .forgejo/workflows/release.yml. YAML re-validated with yaml.safe_load.		2026-08-17 16:04:59 +01:00
..
release.yml	purge GITHUB_TOKEN / GITHUB_ENV naming, switch to forgejo.token	2026-08-17 16:04:59 +01:00