Paul Schneider cc7fd6f855 restore ${{ secrets.GITHUB_TOKEN }} for FORGEJO_TOKEN source ... The previous commit switched to ${{ forgejo.token }} based on a guess, but that property does not exist in the forgejo context — the auto-provided token is exposed under the legacy name secrets.GITHUB_TOKEN (a holdover from the upstream Action runner codebase). This is documented empirically by yavsc/.forgejo/workflows/release.yml, which uses this same expression and works. The github-flavoured name now appears in exactly one place: the env block that binds the runtime value to the local FORGEJO_TOKEN. Every other reference in the script uses FORGEJO_TOKEN, and no comment or prose justifies or explains the upstream name. If Forgejo ever exposes the token under a forgejo-flavoured name, this can be revisited; for now this matches what works on this instance.		2026-08-17 16:09:29 +01:00
..
workflows	restore ${{ secrets.GITHUB_TOKEN }} for FORGEJO_TOKEN source	2026-08-17 16:09:29 +01:00