Repository navigation
feat: publish container image to Docker Hub alongside GHCR - #193
Merged
Merged
Conversation
Adds owasp/docksec on Docker Hub as a second push target in publish-container-image.yml, using the same multi-arch build and tag set already computed for GHCR. Also fixes an invalid enable attribute in the metadata-action tags block that surfaced when the workflow is triggered directly via workflow_dispatch (inputs.publish_latest is unset in that path, which rendered as an empty string instead of a boolean).
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
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.
Summary
owasp/docksecon Docker Hub as a second push target inpublish-container-image.yml, reusing the same multi-arch build and tag set already computed for GHCRenableattribute in the metadata-action tags block that surfaced when the workflow is triggered directly viaworkflow_dispatch(inputs.publish_latestis unset in that path and rendered as an empty string instead of a boolean)publish-to-pypi.ymlnow forwardsDOCKERHUB_USERNAME/DOCKERHUB_TOKENsecrets to the reusable workflowRequires before merge/run
DOCKERHUB_USERNAMEandDOCKERHUB_TOKENmust exist (Docker Hub access token with Read & Write scope)Test plan
tag: 2026.9.21and confirm bothghcr.io/owasp/docksec:2026.9.21andowasp/docksec:2026.9.21are pushed