v0.10.0-beta8 release is incomplete: controller + app images and Helm chart not published to ghcr

[elihai-risk]

Summary

The v0.10.0-beta8 git tag exists, but its release artifacts on ghcr.io are incomplete: the controller and app images and the Helm chart were never published, while ui and skills-init were. There is also no GitHub Release for the tag. This makes v0.10.0-beta8 uninstallable/unupgradable.

What I observed (anonymous ghcr pull, 2026-07-16)

Artifact	0.10.0-beta7	0.10.0-beta8
kagent-dev/kagent/controller	200	404
kagent-dev/kagent/app	200	404
kagent-dev/kagent/ui	200	200
kagent-dev/kagent/skills-init	200	200
kagent-dev/kagent/helm/kagent	200	404

tok=$(curl -s "https://ghcr.io/token?scope=repository:kagent-dev/kagent/controller:pull" | jq -r .token)
curl -s -o /dev/null -w "%{http_code}\n" -H "Authorization: Bearer $tok" \
  -H "Accept: application/vnd.oci.image.index.v1+json" \
  https://ghcr.io/v2/kagent-dev/kagent/controller/manifests/0.10.0-beta8
# => 404

gh release view v0.10.0-beta8 → release not found. The published OCI tag list for both .../app and .../helm/kagent tops out at 0.10.0-beta7.

Why it matters

v0.10.0-beta8 is the first tag containing #2242 (declarative agents reference their runtime image by tag rather than the baked digest — fixes #2055). Adopters mirroring images into a private registry specifically need beta8+ to get that behavior, but with the controller, app, and chart artifacts missing there is no way to install or upgrade to it. beta7 does not contain #2242, so there is no earlier fallback that has the fix.

Expected

Either the release workflow completes and publishes the missing controller + app images and the helm/kagent chart for 0.10.0-beta8 (plus a GitHub Release), or a subsequent fully-published tag supersedes it.

Environment

• Consuming the published ghcr images/chart (not building from source).
• Verified against ghcr.io/kagent-dev/kagent/* on 2026-07-16.