Repository navigation
Conversation
|
Looks like Docker also want you to replace line:4 of Dockerfile From: |
Owner
Author
|
This PR's proposed change isn't necessary - I've added |
This branch has not been deployed
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
2 participants
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.
Why
The v0.11.0 release published successfully to RubyGems but container publication stopped because
DOCKERHUB_USERNAMEwas never configured. The existing Docker Hub token belongs to the fixedsj26namespace.What
Uses the non-secret
sj26username directly in the release workflow and updates the setup guide to require only the protectedDOCKERHUB_TOKENenvironment secret. The documented warning about the personal token's account-wide authority remains explicit.