Repository navigation
Use SBX_USERNAME and SBX_TOKEN secrets for sbx login - #596
Merged
Merged
Conversation
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
marked this pull request as ready for review
November 18, 2026 02:20
Contributor
Overview
Policies (0 improved, 0 worsened)Health score:
Packages and Vulnerabilities (1 package changes and 0 vulnerability changes)
Changes for packages of type
|
| Package | Versionscore-compose:latest |
Versionscore-compose:latest |
|
|---|---|---|---|
| ♾️ | github.com/score-spec/score-compose | 0.0.0-20261118020053-f264cc7796f8+dirty |
0.0.0-20261118021821-54e50ee35898+dirty |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The
upgrade-go-versionworkflow'ssbx loginstep now readsSBX_USERNAMEandSBX_TOKENrepository secrets instead ofDOCKER_HUB_USERNAMEandDOCKER_HUB_TOKEN.What does this PR do?
Gives the Docker Sandboxes login its own credentials. The last run (44220140841) failed at
sbx loginwithinvalid Docker credentials.SBX_TOKENis meant to be a Docker personal access token, withSBX_USERNAMEthe Docker ID that owns it..github/dependabot.ymlis unchanged: it keeps using theDOCKER_HUB_*Dependabot secrets for registry access.Not verified: the workflow has not been run with the new secrets.
Types of changes
Checklist:
AI usage disclosure:
🤖 Generated with Claude Code