Skip to content

Use SBX_USERNAME and SBX_TOKEN secrets for sbx login - #596

Merged
mathieu-benoit merged 1 commit into
mainfrom
sbx-login-secrets
Nov 18, 2026
Merged

mathieu-benoit merged 1 commit into
mainfrom
sbx-login-secrets

Conversation

@mathieu-benoit

Copy link
Copy Markdown
Contributor

Description

The upgrade-go-version workflow's sbx login step now reads SBX_USERNAME and SBX_TOKEN repository secrets instead of DOCKER_HUB_USERNAME and DOCKER_HUB_TOKEN.

What does this PR do?

Gives the Docker Sandboxes login its own credentials. The last run (44220140841) failed at sbx login with invalid Docker credentials. SBX_TOKEN is meant to be a Docker personal access token, with SBX_USERNAME the Docker ID that owns it.

.github/dependabot.yml is unchanged: it keeps using the DOCKER_HUB_* Dependabot secrets for registry access.

Not verified: the workflow has not been run with the new secrets.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • New chore (expected functionality to be implemented)

Checklist:

  • My change requires a change to the documentation.
    • I have updated the documentation accordingly.
  • I've signed off with an email address that matches the commit author.

AI usage disclosure:

  • AI was used
    • I understand every change.
    • Briefly describe how AI was used: This PR was written in part with the assistance of generative AI (Claude Code), which made the rename.

🤖 Generated with Claude Code

Read the sbx login credentials from dedicated SBX_USERNAME and SBX_TOKEN
repository secrets instead of DOCKER_HUB_USERNAME and DOCKER_HUB_TOKEN.
The Dependabot registry config keeps using the DOCKER_HUB_* Dependabot
secrets.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Mathieu Benoit <mathieu-benoit@hotmail.fr>
@mathieu-benoit
mathieu-benoit marked this pull request as ready for review November 18, 2026 02:20
@github-actions

github-actions Bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Overview

Image reference score-compose:latest score-compose:latest
- digest fa4dda196ea4 464b33b14ee3
- tag latest latest
- provenance f264cc7 54e50ee
- vulnerabilities critical: 0 high: 0 medium: 0 low: 0 critical: 0 high: 0 medium: 0 low: 0
- platform linux/amd64 linux/amd64
- size 7.2 MB 7.2 MB (+15 B)
- packages 53 53
Base Image static:20261020-alpine3.24 static:20261020-alpine3.24
- vulnerabilities
Policies (0 improved, 0 worsened)

Health score: score-compose:latest B (83%) → score-compose:latest B (83%)

Policy Name score-compose:latest score-compose:latest Change Standing
Default non-root user ✅ ✅ No Change
No copyleft licenses ⚠️ 2 ⚠️ 2 No Change
No fixable critical or high vulnerabilities ✅ ✅ No Change
No high-profile vulnerabilities ✅ ✅ No Change
No outdated base images ⚠️ ⚠️ No Change
No unapproved base images ✅ ✅ No Change
Supply chain attestations ✅ ✅ No Change
Packages and Vulnerabilities (1 package changes and 0 vulnerability changes)
  • ♾️ 1 packages changed
  • 52 packages unchanged
Changes for packages of type golang (1 changes)
Package Version
score-compose:latest
Version
score-compose:latest
♾️ github.com/score-spec/score-compose 0.0.0-20261118020053-f264cc7796f8+dirty 0.0.0-20261118021821-54e50ee35898+dirty

@mathieu-benoit
mathieu-benoit merged commit 51ff1ff into main Nov 18, 2026
19 checks passed
@mathieu-benoit
mathieu-benoit deleted the sbx-login-secrets branch November 18, 2026 02:23
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.

1 participant