Cursus publishes its broker container image to GitHub Container Registry (GHCR) through .github/workflows/docker-publish.yml.
The upstream image is:
ghcr.io/cursus-io/cursus
Each published tag is a manifest list containing linux/amd64 and
linux/arm64 images built from the repository Dockerfile.
The publishing workflow runs on:
main;v*; andworkflow_dispatch runs.docker/metadata-action generates the published tags:
| Source | Tags |
|---|---|
main push |
main, latest, and sha-<short-sha> |
Semantic version tag such as v0.2.0 |
0.2.0, 0.2, latest, and sha-<short-sha> |
| Manual run | Ref and SHA tags allowed by the metadata rules |
The workflow:
ghcr.io with the workflow-scoped GITHUB_TOKEN;The Docker build embeds the exact Git commit in the broker binary and writes
it to the OCI org.opencontainers.image.revision label. The cluster Helm chart
requires both the immutable manifest digest and this revision, then runs the
broker’s deployment-contract check before starting any member.
The job uses read-only repository contents permission and packages: write. The repository organization owns the package. Package visibility and anonymous pull access are managed separately in the GitHub package settings.
The repository currently publishes container images only. It does not create GitHub Releases, cross-compile binary archives, or upload checksums.
After a successful workflow run:
docker pull ghcr.io/cursus-io/cursus:latest
docker inspect ghcr.io/cursus-io/cursus:latest
For a version tag, replace latest with the normalized semantic version, for example 0.2.0.