You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Browse filesBrowse the repository at this point in the historyBrowse files
tazhate
committed
fix(release): add OCI labels so GHCR image binds to repo Packages
Root cause of the persistent 403 from `helm install`:
1. The image was being pushed to ghcr.io without
`org.opencontainers.image.source` labels.
2. Without that label GHCR creates the package as orphaned — the buildx
`--push` step reports success, but the package never appears in the
repository's Packages sidebar and inherits no visibility from the repo
(so it stays effectively private and anonymous pulls 403).
3. The Helm chart push (`helm push oci://...`) automatically writes the
source label, which is why `charts/chainplane` showed up in the UI but
the operator container did not.
Fix:
- Dockerfile: explicit OCI labels on the final stage (source, url, title,
description, licenses, documentation).
- release.yml: same labels added via docker/build-push-action `labels:`,
plus dynamic `version` / `revision` derived from `github.ref_name` /
`github.sha`. Disabled `provenance` and `sbom` attestations as they
produce extra manifests that confuse the Packages UI auto-binding.
Bumped to v0.2.2 since the previous tag's image is unrecoverable (already
pushed without labels — has to be republished as a new tag).
Context: spent ~30min reproducing — confirmed via /v2 API that the image
exists (401 unauthorized, not 404), but the GitHub UI didn't index it
because of missing repo association via the `image.source` label.
Signed-off-by: tazhate <hate@tazhate.ru>
0 commit comments