ci: Migrate release off RELEASE_TOKEN to job GITEA_TOKEN #26
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Draft for review — do not implement/merge without Eva review
Migrate CI release off legacy
secrets.RELEASE_TOKENto the job built-in token (secrets.GITEA_TOKEN/ runnerGITEA_TOKEN).Policy (Eva / Rex CI token policy)
secrets.GITEA_TOKENwith jobpermissions: contents: write.GITEA_TOKEN: ${{ secrets.GITEA_TOKEN }}andGORELEASER_FORCE_TOKEN: gitea(and typically mirror intoGITHUB_TOKENthe same way vulture does).gitea-release-action@v1when not using GoReleaser.RELEASE_TOKENPAT.RELEASE_TOKENis known legacy — replace with job token; do not refresh/extend that PAT.Reference implementations (already migrated)
s1d3sw1ped/vulture(.gitea/workflows/release-tag.yaml)s1d3sw1ped/scratchbox,s1d3sw1ped/helix-proxy,s1d3sw1ped/SwipedModSwitcher,s1d3sw1ped/grok-bot-binStatus
DRAFT — open for Eva review only. No PR/merge until approved.
Already migrated: release workflows use secrets.GITEA_TOKEN with contents: write; no RELEASE_TOKEN left.