.gitea/workflows: Prefer job GITEA_TOKEN #27
No reviewers
Labels
No labels
blocked
bug
draft
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
s1d3sw1ped/steamcache2!27
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ash/ci-gitea-token-release"
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?
What
Update
.gitea/workflows/release-tag.yamlso the release job uses the built-in job token instead of legacysecrets.RELEASE_TOKEN:permissions: contents: writeGITEA_TOKEN/GITHUB_TOKENfrom${{ secrets.GITEA_TOKEN }}GORELEASER_FORCE_TOKEN: giteaWhy
steamcache2 still wired release to a legacy RELEASE_TOKEN PAT. Eva/Rex CI token policy prefers
secrets.GITEA_TOKENwithcontents: write(same pattern as vulture). An empty Secrets UI entry forGITEA_TOKENis normal — the runner injects the job token.Issue: #26
Test
ci: Migrate release to job GITEA_TOKENto .gitea/workflows: Prefer job GITEA_TOKEN