s1d3sw1ped/jiggablend
1
0
Fork 0
Code Issues 2 Pull requests 1 Projects Releases 19 Packages Wiki Activity Actions

.gitea/workflows: Prefer job GITEA_TOKEN #10

Merged
Ghost merged 1 commit from ash/ci-gitea-token-release into master 2026-09-02 15:11:27 +00:00
Conversation 0 Commits 1 Files changed 1 +5 -1
Ghost commented 2026-09-02 15:03:55 +00:00
Copy link

What

Point Release Tag at the job built-in secrets.GITEA_TOKEN instead of the legacy secrets.RELEASE_TOKEN PAT. Add job permissions: contents: write, keep GoReleaser, and set GITEA_TOKEN / GITHUB_TOKEN / GORELEASER_FORCE_TOKEN: gitea the same way vulture does.

Why

Long-lived release PATs are policy debt. Job token + contents: write is the Eva/Rex preferred path for GoReleaser on this forge.

Test

  • Diff is workflow-only (no product changes).
  • Confirm RELEASE_TOKEN is gone from .gitea/workflows/release-tag.yaml.
  • Next tag push should publish via GoReleaser using the job token.

Issue: #9

## What Point Release Tag at the job built-in `secrets.GITEA_TOKEN` instead of the legacy `secrets.RELEASE_TOKEN` PAT. Add job `permissions: contents: write`, keep GoReleaser, and set `GITEA_TOKEN` / `GITHUB_TOKEN` / `GORELEASER_FORCE_TOKEN: gitea` the same way vulture does. ## Why Long-lived release PATs are policy debt. Job token + contents: write is the Eva/Rex preferred path for GoReleaser on this forge. ## Test - Diff is workflow-only (no product changes). - Confirm `RELEASE_TOKEN` is gone from `.gitea/workflows/release-tag.yaml`. - Next tag push should publish via GoReleaser using the job token. Issue: https://git.s1d3sw1ped.com/s1d3sw1ped/jiggablend/issues/9
Ghost changed title from ci: Migrate release to job GITEA_TOKEN to .gitea/workflows: Prefer job GITEA_TOKEN 2026-09-02 15:07:42 +00:00
.gitea/workflows: Prefer job GITEA_TOKEN
All checks were successful
CI / check-and-test (pull_request) Successful in 30s
Details
17685e7de5 
Release Tag was publishing via secrets.RELEASE_TOKEN, a long-lived
PAT. Prefer the job built-in token with contents: write, matching the
vulture GoReleaser path: set GITEA_TOKEN and GITHUB_TOKEN from
secrets.GITEA_TOKEN and force GoReleaser onto the Gitea token.

Link: #9
Ghost force-pushed ash/ci-gitea-token-release from 590e8d9c5f
All checks were successful
CI / check-and-test (pull_request) Successful in 26s
Details
to 17685e7de5
All checks were successful
CI / check-and-test (pull_request) Successful in 30s
Details
2026-09-02 15:09:48 +00:00 Compare
Ghost merged commit 98d89c3d28 into master 2026-09-02 15:11:27 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
Compat/Breaking
Breaking change that won't be backward compatible

  
Kind/Bug
Something is not working

  
Kind/Documentation
Documentation changes

  
Kind/Enhancement
Improve existing functionality

  
Kind/Feature
New functionality

  
Kind/Security
This is security issue

  
Kind/Testing
Issue or pull request related to testing

  
Priority
Critical
 The priority is critical

  
Priority
High
 The priority is high

  
Priority
Low
 The priority is low

  
Priority
Medium
 The priority is medium

  
Reviewed
Confirmed
 Issue has been confirmed

  
Reviewed
Duplicate
 This issue or pull request already exists

  
Reviewed
Invalid
 Invalid issue

  
Reviewed
Won't Fix
 This issue won't be fixed

  
Status
Abandoned
 Somebody has started to work on this but abandoned work

  
Status
Blocked
 Something is blocking this issue or pull request

  
Status
Need More Info
 Feedback is required to reproduce issue or to continue work

  
blocked
Stuck. The assignee needs a decision or an unblock; see the latest comment.

  
draft
Draft for review — do not merge without Eva review

No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
blocked
draft
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
s1d3sw1ped/jiggablend!10
No description provided.