Use org-level REGISTRY_USERNAME/REGISTRY_PASSWORD secrets

Replace DOCKERHUB_USERNAME/DOCKERHUB_TOKEN with the existing org-level
secrets. Use automatic GITHUB_TOKEN for Gitea release creation.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Mathias Beaulieu-Duncan 2026-02-09 18:03:12 -05:00
parent 19db31b717
commit 0d4f4cc50f
2 changed files with 5 additions and 6 deletions

View File

@ -29,8 +29,8 @@ jobs:
- name: Login to Docker Hub
uses: docker/login-action@v3
with:
username: ${{ secrets.DOCKERHUB_USERNAME }}
password: ${{ secrets.DOCKERHUB_TOKEN }}
username: ${{ secrets.REGISTRY_USERNAME }}
password: ${{ secrets.REGISTRY_PASSWORD }}
- name: Extract version tag
id: version
@ -96,7 +96,7 @@ jobs:
release-dir: .
release-notes-assistant: none
env:
GITHUB_TOKEN: ${{ secrets.GITEA_TOKEN }}
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
- name: Clean up
if: always()

View File

@ -47,9 +47,8 @@ A weekly scheduled workflow checks for new Talos and RPi kernel releases and cre
| Secret | Description |
|--------|-------------|
| `DOCKERHUB_USERNAME` | Docker Hub username |
| `DOCKERHUB_TOKEN` | Docker Hub access token |
| `GITEA_TOKEN` | Gitea API token (for creating releases and issues) |
| `REGISTRY_USERNAME` | Docker Hub username (org-level) |
| `REGISTRY_PASSWORD` | Docker Hub access token (org-level) |
## Runner Setup (ASUS GX10)