keyop-go/nfq_forwarder
1
0
Fork 0
Code Issues 3 Pull requests 1 Projects Releases 21 Packages Wiki Activity Actions

Set GORELEASER_FORCE_TOKEN=gitea for the release job (#40) #81

Merged
danny merged 1 commit from issue40_goreleaser_force_token into main 2026-07-09 13:21:08 +01:00
Conversation 1 Commits 1 Files changed 1 +6
claude commented 2026-07-09 13:15:18 +01:00
Collaborator
Copy link

The real v1.1.6 tag push (first live test of the release path) got past checkout, build, and packaging, then failed with:

multiple tokens found, but only one is allowed: GITHUB_TOKEN, GITEA_TOKEN

Forgejo Actions always injects its own GITHUB_TOKEN (used by actions/checkout's own auth) - goreleaser auto-detects the SCM provider by scanning for recognised token env vars, and refuses to guess when it finds more than one. GORELEASER_FORCE_TOKEN=gitea disambiguates explicitly.

v1.1.6 never actually published anything (failed before the publish step ran), so once this merges I'll move to v1.1.7 for the release rather than trying to reuse/move the v1.1.6 tag.

The real v1.1.6 tag push (first live test of the release path) got past checkout, build, and packaging, then failed with: ``` multiple tokens found, but only one is allowed: GITHUB_TOKEN, GITEA_TOKEN ``` Forgejo Actions always injects its own `GITHUB_TOKEN` (used by `actions/checkout`'s own auth) - goreleaser auto-detects the SCM provider by scanning for recognised token env vars, and refuses to guess when it finds more than one. `GORELEASER_FORCE_TOKEN=gitea` disambiguates explicitly. v1.1.6 never actually published anything (failed before the publish step ran), so once this merges I'll move to v1.1.7 for the release rather than trying to reuse/move the v1.1.6 tag.
claude self-assigned this 2026-07-09 13:15:18 +01:00
Set GORELEASER_FORCE_TOKEN=gitea for the release job (#40)
All checks were successful
CI / lint (push) Successful in 24s
Details
CI / build (push) Successful in 26s
Details
CI / lint (pull_request) Successful in 25s
Details
CI / build (pull_request) Successful in 26s
Details
CI / release (push) Has been skipped
Details
CI / release (pull_request) Has been skipped
Details
6504a42ee6 
Real tag push (v1.1.6) surfaced this: Forgejo Actions always injects its
own GITHUB_TOKEN (mirroring GitHub Actions, used by actions/checkout's
own auth) - goreleaser scans the environment for any of several
recognised token vars to auto-detect the SCM provider, and refuses to
guess when it finds more than one:

  multiple tokens found, but only one is allowed: GITHUB_TOKEN, GITEA_TOKEN

GORELEASER_FORCE_TOKEN=gitea disambiguates explicitly. lint/build and
checkout/build-packaging within the release job itself all already
succeeded on this same real tag push - this was the last failure before
goreleaser would have actually tried to publish.
danny requested review from danny 2026-07-09 13:16:06 +01:00
danny approved these changes 2026-07-09 13:16:18 +01:00
danny left a comment
Copy link

LGTM

LGTM
danny merged commit 74690d99e4 into main 2026-07-09 13:21:08 +01:00
danny deleted branch issue40_goreleaser_force_token 2026-07-09 13:21:08 +01:00
Sign in to join this conversation.
Reviewers
No reviewers
danny
Labels
Clear labels   
Bug

   
BuildIssue

   
Claude-fixed

   
Enhancement

   
In Progress

   
Low priority

   
On Hold
Blocked on something outside this project (e.g. external infrastructure) - not actionable right now

  
Rejected
Feature or ussue was rejected for development

  
Security
No labels
Bug
BuildIssue
Claude-fixed
Enhancement
In Progress
Low priority
On Hold
Rejected
Security
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
claude
2 participants
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
keyop-go/nfq_forwarder!81
No description provided.