Skip to content

ci: update registry auth credentials#1007

Merged
crazy-max merged 4 commits into
docker:masterfrom
crazy-max:ci-creds-update
Jun 9, 2026
Merged

ci: update registry auth credentials#1007
crazy-max merged 4 commits into
docker:masterfrom
crazy-max:ci-creds-update

Conversation

@crazy-max

Copy link
Copy Markdown
Member

This updates CI login coverage to use the current registry hosts and Docker public bot credentials.

The workflow now uses fixed ACR, ECR, and GAR registry endpoints, and Docker Hub login steps now authenticate with DOCKERPUBLICBOT_USERNAME and DOCKERPUBLICBOT_READ_PAT.

The previous workflow depended on older secret names for Docker Hub credentials and registry host construction, which makes the CI setup harder to keep aligned with the current repository secrets and registry configuration.

@crazy-max crazy-max marked this pull request as ready for review June 4, 2026 12:36
crazy-max added 4 commits June 4, 2026 16:19
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
Comment thread .github/workflows/ci.yml
Comment on lines -150 to +151
username: ${{ secrets.DOCKERHUB_USERNAME }}
password: ${{ secrets.DOCKERHUB_TOKEN }}
username: ${{ vars.DOCKERPUBLICBOT_USERNAME }}
password: ${{ secrets.DOCKERPUBLICBOT_READ_PAT }}

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Still not convinced this is better; feels like this is increasing the blast area.

@crazy-max crazy-max merged commit 946f94d into docker:master Jun 9, 2026
11 checks passed
@crazy-max crazy-max deleted the ci-creds-update branch June 9, 2026 08:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants