Skip to content

fix(ci): emit GHCR package description as index annotation #39

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
strausmann merged 1 commit into from
May 10, 2026
+13 −0
Merged

fix(ci): emit GHCR package description as index annotation #39

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions .github/workflows/docker-publish.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,14 @@ permissions:

env:
REGISTRY_GHCR: ghcr.io
# By default docker/metadata-action emits annotations with the `manifest:`
# prefix only — that lands on per-platform manifests but NOT on the multi-
# arch manifest list (the "index"). GHCR's package UI reads the package
# description from `index:org.opencontainers.image.description`; without
# the index level, the package page shows "No description provided".
# Setting this env var makes the action emit BOTH levels so per-platform
# inspectors and registry UIs see the metadata.
DOCKER_METADATA_ANNOTATIONS_LEVELS: manifest,index

jobs:
publish:
Expand Down Expand Up @@ -115,6 +123,11 @@ jobs:
push: true
tags: ${{ steps.meta.outputs.tags }}
labels: ${{ steps.meta.outputs.labels }}
# Pass through the annotations metadata-action computed (with both
# manifest:* and index:* levels, see DOCKER_METADATA_ANNOTATIONS_LEVELS
# at the workflow root). Without this the package shows up on GHCR
# with "No description provided".
annotations: ${{ steps.meta.outputs.annotations }}
# Build-args flow into the Dockerfile's ARG VERSION / REVISION /
# BUILD_DATE, which the Dockerfile then bakes into both OCI image
# labels (via LABEL) and runtime ENV vars (HUB_VERSION, …) so the
Expand Down