actions-marketplace-validations/Openzim Docker Publish Action

Build and publish Docker Images to both Docker Hub and ghcr.

Trust Signals

workflow.ymlSHA-pinned

uses: actions-marketplace-validations/openzim_docker-publish-action@64f383ddafdd61445f348b1ad61ae9a33a956702 # no releases — HEAD as of 2026-07-13

tags can be moved; commit SHAs can't. why a SHA?

name	description	required	default
image-name	target image path on both registries (ex. 'openzim/dnscache')	yes	—
registries	list of registries to push to (defaults to docker.io ghcr.io)	no	ghcr.io
credentials	list of credentials for each registry. Ex. DOCKERIO_USERNAME=xxx DOCKERIO_TOKEN=yyy GHCRIO_USERNAME=xxx	yes	—
context	folder to use as context for the build (ex. '.' or 'dnscache')	no	.
dockerfile	Dockerfile path (relative to context) if not 'Dockerfile'	no	Dockerfile
build-args	optional key/value pairs to pass as build arguments. {tag} replaced with found version (if any)	no	—
platforms	specify platform to build for (one of linux/amd64, linux/arm64, linux/riscv64, linux/ppc64le, linux/s390x, linux/386, linux/arm/v7, linux/arm/v6, etc)	no	linux/amd64
on-master	tag to use on master commits. (ex. 'latest' or 'dev') Leave out if not wanted	no	—
tag-pattern	pattern to trigger image tagging (ex. 'dnscache-v*')	no	—
latest-on-tag	should matched tag (or manual-tag) be tagged as 'latest' also? (true or false)	no	false
manual-tag	Specify the tag manually. Overrides on-master and tag-pattern.	no	""
restrict-to	repository path to limit this action to (ex. 'openzim/zimfarm') to prevent forks from triggering it.	no	—
webhook	URL to request (POST) to after a sucessful push to registry•ies	no	""
repo_description	Text to set as repository description on docker.io (100 chars max)	no	—
repo_overview	Text (markdown) to set as repository overview on docker.io (2.5MB max)	no	—

no outputs