fmartingr/smtp2shoutrrr
Watch
1
0
Fork
You've already forked smtp2shoutrrr
 0
Code Issues 3 Pull requests 1 Projects Releases 7 Packages 1 Wiki Activity Actions

ci: rename the FORGEJO_TOKEN secret to ACTIONS_TOKEN (FMG-6) #12

Merged
fmartingr merged 1 commit from agent/full-stack-developer/fmg-6-actions-token into main 2026-09-08 20:09:54 +02:00
Conversation 0 Commits 1 Files changed 1 +2 -2
butterrobot commented 2026-09-08 19:59:57 +02:00
Collaborator
Copy link

Both secrets.FORGEJO_TOKEN references in .github/workflows/release.yml are now secrets.ACTIONS_TOKEN: the registry login password and the GITEA_TOKEN handed to GoReleaser. Those were the only two occurrences anywhere in the repository — nothing else, including the README and the goreleaser config, named the secret.

Nothing else about the release job changes: -u ${{ github.actor }} and GORELEASER_FORCE_TOKEN: gitea are untouched.

Needs a secret to exist before the next tag

The rename only redirects which secret the job reads. ACTIONS_TOKEN has to be defined on the repository (or its owner/org) with the same reach the release needs — write:package on git.nakama.town/fmartingr/, plus repo write for the release upload — or the release job will get an empty value and repeat the 401 Unauthorized: reqPackageAccess failure from FMG-5. Note that the login step will still print Login Succeeded in that case, for the reason described on #10.

I could not verify the secret exists: tea actions secret list refuses for this credential (user should be the owner of the repo), and Forgejo does not expose a secret's value, owner, or scopes through the API.

Checks

CI-config change only, no Go code touched. I parsed both workflow files to confirm they are still valid YAML and that the release job's env block resolves to GITEA_TOKEN: ${{ secrets.ACTIONS_TOKEN }}. There is no Go toolchain, golangci-lint, or goreleaser in this environment, so the repository's format / lint / test / build / check targets were not run locally — CI covers them on this PR.

Closes FMG-6

Both `secrets.FORGEJO_TOKEN` references in `.github/workflows/release.yml` are now `secrets.ACTIONS_TOKEN`: the registry login password and the `GITEA_TOKEN` handed to GoReleaser. Those were the only two occurrences anywhere in the repository — nothing else, including the README and the goreleaser config, named the secret. Nothing else about the release job changes: `-u ${{ github.actor }}` and `GORELEASER_FORCE_TOKEN: gitea` are untouched. ## Needs a secret to exist before the next tag The rename only redirects which secret the job reads. `ACTIONS_TOKEN` has to be defined on the repository (or its owner/org) with the same reach the release needs — `write:package` on `git.nakama.town/fmartingr/`, plus repo write for the release upload — or the release job will get an empty value and repeat the `401 Unauthorized: reqPackageAccess` failure from FMG-5. Note that the login step will still print `Login Succeeded` in that case, for the reason described on #10. I could not verify the secret exists: `tea actions secret list` refuses for this credential (`user should be the owner of the repo`), and Forgejo does not expose a secret's value, owner, or scopes through the API. ## Checks CI-config change only, no Go code touched. I parsed both workflow files to confirm they are still valid YAML and that the release job's env block resolves to `GITEA_TOKEN: ${{ secrets.ACTIONS_TOKEN }}`. There is no Go toolchain, golangci-lint, or goreleaser in this environment, so the repository's `format` / `lint` / `test` / `build` / `check` targets were not run locally — CI covers them on this PR. Closes FMG-6
ci: rename the FORGEJO_TOKEN secret to ACTIONS_TOKEN (FMG-6)
All checks were successful
CI / goreleaser-lint (pull_request) Successful in 4s
Details
CI / format (pull_request) Successful in 2m34s
Details
CI / lint (pull_request) Successful in 2m56s
Details
CI / test (pull_request) Successful in 2m44s
Details
CI / build (pull_request) Successful in 2m39s
Details
37e03762dd 
The release job read the registry login password and GITEA_TOKEN from
secrets.FORGEJO_TOKEN. Both now read secrets.ACTIONS_TOKEN.

Closes FMG-6
fmartingr deleted branch agent/full-stack-developer/fmg-6-actions-token 2026-09-08 20:09:54 +02: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

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
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
fmartingr/smtp2shoutrrr!12
No description provided.