Make legacy Docker publishing manual - #23
Merged
Merged
Conversation
Release tags triggered a Docker Hub job for the legacy gptcode/cli image, but this repository has no Docker Hub credentials. Every otherwise valid GitHub release would therefore include an unrelated failed workflow. Keep the workflow available through workflow_dispatch while removing the tag trigger. GitHub releases remain automated through GoReleaser and the repository-scoped GITHUB_TOKEN. If a maintained container distribution is needed later, define its owner, registry, credentials, and support contract before restoring automatic publication.
jadercorrea
marked this pull request as ready for review
July 28, 2026 16:46
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
1 participant
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
Every semantic-version tag triggered two independent publication paths. The maintained GitHub release uses GoReleaser and the repository-scoped
GITHUB_TOKEN, but the Docker job targets the legacydocker.io/gptcode/clinamespace and requires secrets that do not exist in this repository.That would make a valid CLI release appear partially broken for a distribution channel that is not currently maintained.
What changed
Remove the tag trigger from the Docker Hub workflow while retaining
workflow_dispatch. Docker publishing remains available as an explicit manual operation if ownership and credentials are restored.The GitHub release workflow remains unchanged and continues to run
make verifybefore publishing cross-platform archives and checksums.Validation
make verify