s1d3sw1ped/teleport
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 4 Wiki Activity

ci: Migrate release off RELEASE_TOKEN to job GITEA_TOKEN #11

New Issue
Closed
opened 2026-09-02 09:54:32 -05:00 by Ghost · 1 comment
Ghost commented 2026-09-02 09:54:32 -05:00
Copy Link
Copy Source

Draft for review — do not implement/merge without Eva review

Migrate CI release off legacy secrets.RELEASE_TOKEN to the job built-in token (secrets.GITEA_TOKEN / runner GITEA_TOKEN).

Policy (Eva / Rex CI token policy)

  • Prefer secrets.GITEA_TOKEN with job permissions: contents: write.
  • For GoReleaser: set GITEA_TOKEN: ${{ secrets.GITEA_TOKEN }} and GORELEASER_FORCE_TOKEN: gitea (and typically mirror into GITHUB_TOKEN the same way vulture does).
  • Prefer gitea-release-action@v1 when not using GoReleaser.
  • Do not invent a new RELEASE_TOKEN PAT.
  • On steamcache2, RELEASE_TOKEN is known legacy — replace with job token; do not refresh/extend that PAT.

Reference implementations (already migrated)

  • GoReleaser path: s1d3sw1ped/vulture (.gitea/workflows/release-tag.yaml)
  • release-action path: s1d3sw1ped/scratchbox, s1d3sw1ped/helix-proxy, s1d3sw1ped/SwipedModSwitcher, s1d3sw1ped/grok-bot-bin

Status

DRAFT — open for Eva review only. No PR/merge until approved.

## Draft for review — do not implement/merge without Eva review Migrate CI release off legacy `secrets.RELEASE_TOKEN` to the job built-in token (`secrets.GITEA_TOKEN` / runner `GITEA_TOKEN`). ### Policy (Eva / Rex CI token policy) - Prefer **`secrets.GITEA_TOKEN`** with job **`permissions: contents: write`**. - For **GoReleaser**: set `GITEA_TOKEN: ${{ secrets.GITEA_TOKEN }}` and `GORELEASER_FORCE_TOKEN: gitea` (and typically mirror into `GITHUB_TOKEN` the same way vulture does). - Prefer **`gitea-release-action@v1`** when not using GoReleaser. - **Do not invent** a new `RELEASE_TOKEN` PAT. - On **steamcache2**, `RELEASE_TOKEN` is known legacy — replace with job token; do not refresh/extend that PAT. ### Reference implementations (already migrated) - GoReleaser path: `s1d3sw1ped/vulture` (`.gitea/workflows/release-tag.yaml`) - release-action path: `s1d3sw1ped/scratchbox`, `s1d3sw1ped/helix-proxy`, `s1d3sw1ped/SwipedModSwitcher`, `s1d3sw1ped/grok-bot-bin` ### Status **DRAFT** — open for Eva review only. No PR/merge until approved.
Ghost added the draft label 2026-09-02 09:54:32 -05:00
Ghost commented 2026-09-02 11:16:01 -05:00
Copy Link
Copy Source

Already migrated: release workflows use secrets.GITEA_TOKEN with contents: write; no RELEASE_TOKEN left.

Already migrated: release workflows use secrets.GITEA_TOKEN with contents: write; no RELEASE_TOKEN left.
Ghost closed this issue 2026-09-02 11:16:02 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
 draft
Draft for review — do not merge without Eva review
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No Label draft
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
ash blake eva linus moss pike s1d3sw1ped
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: s1d3sw1ped/teleport#11
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?