Two defects in the manual Helm Publish path (gh-release-chart.yml), both found while republishing kedify-agent/v0.6.8:
-
Release tag mismatch: the Upload image digest asset step uploads to ${{ steps.push_tag.outputs.new_tag }} = kedify-agent-v0.6.8 (hyphen, from the tag-push step), but releases created by the milestones tracker use the kedify-agent/v0.6.8 (slash) tag — so the upload fails with release not found whenever the release came from the tracker path (run 30641426529). The chart publish itself succeeds; only the asset step dies.
-
Silently empty generated-images.json: the kedify-agent/v0.6.7 release asset contains "images": [] — the air-gapped image list generation produced an empty list in CI without failing the run. Regenerating locally for v0.6.8 (helm deps built + yq present) yields 30 pinned images, uploaded manually. Likely print-image-names.sh failing/short-circuiting silently in the CI environment; it should hard-fail on an empty result.
Longer term both paths (tracker vs manual) duplicating release logic is the root issue — consolidating them is probably part of the broader release-automation work.
Two defects in the manual Helm Publish path (
gh-release-chart.yml), both found while republishingkedify-agent/v0.6.8:Release tag mismatch: the
Upload image digest assetstep uploads to${{ steps.push_tag.outputs.new_tag }}=kedify-agent-v0.6.8(hyphen, from the tag-push step), but releases created by the milestones tracker use thekedify-agent/v0.6.8(slash) tag — so the upload fails withrelease not foundwhenever the release came from the tracker path (run 30641426529). The chart publish itself succeeds; only the asset step dies.Silently empty
generated-images.json: thekedify-agent/v0.6.7release asset contains"images": []— the air-gapped image list generation produced an empty list in CI without failing the run. Regenerating locally for v0.6.8 (helm deps built +yqpresent) yields 30 pinned images, uploaded manually. Likelyprint-image-names.shfailing/short-circuiting silently in the CI environment; it should hard-fail on an empty result.Longer term both paths (tracker vs manual) duplicating release logic is the root issue — consolidating them is probably part of the broader release-automation work.