ci: fix registry auth (use github.token + package permissions) #2

Merged
gsadmin merged 1 commits from development into main 2026-09-02 11:16:43 +00:00
Owner

Registry-auth fix for the release pipeline (run #1 failed at docker login with unauthorized).

  • Use github.token instead of secrets.GITEA_TOKEN (the latter is empty on this instance) for registry login and release creation.
  • Add a permissions block granting contents+packages write to the Actions token.

Merging re-triggers the release workflow.

Registry-auth fix for the release pipeline (run #1 failed at docker login with unauthorized). - Use github.token instead of secrets.GITEA_TOKEN (the latter is empty on this instance) for registry login and release creation. - Add a permissions block granting contents+packages write to the Actions token. Merging re-triggers the release workflow.
gsadmin added 1 commit 2026-09-02 11:16:39 +00:00
The first run failed at docker login with 'unauthorized': secrets.GITEA_TOKEN
is not populated on this instance, so the registry password was empty. Switch
the registry login and release creation to github.token (always injected) and
add an explicit permissions block granting contents+packages write.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
gsadmin merged commit 2514073812 into main 2026-09-02 11:16:43 +00:00
Sign in to join this conversation.
No Reviewers
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: gsadmin/OrchestrAD#2