Skip to content

fix(ci): publish dev Helm charts to the build registry - #5876

Open
matthewgrossman wants to merge 1 commit into
mainfrom
fix/dev-helm-registry/matthewgrossman
Open

matthewgrossman wants to merge 1 commit into
mainfrom
fix/dev-helm-registry/matthewgrossman

Conversation

@matthewgrossman

Copy link
Copy Markdown
Member

Summary

Release Dev can publish binaries and retag images again, but the Helm push still targets the old GHCR namespace and returns HTTP 403. Publish the dev charts alongside the dev images and point the Kubernetes canary at the same registry.

Related Issue

Build fix for Release Helm Chart (OCI, dev).

Changes

  • Publish the floating and SHA-pinned dev charts to ghcr.io/ai-openshell/openshell. Keep the public release destination and version guard unchanged.
  • Package the dev gateway chart with image defaults that match the published runtime images.
  • Authenticate the Kubernetes canary to GHCR with its read-only token and preload the private runtime images into kind. Document the equivalent local steps.

Release Notes

Testing

  • git diff --check and actionlint pass, excluding existing SC2086 and SC2251 notices in the canary workflow.
  • Packaged both charts at floating and SHA-pinned versions, verified all four destinations with stubbed pushes, and rendered both gateway chart versions to check all three runtime image references.
  • Live GHCR publication and the kind canary remain to be verified after merge.

Checklist

  • Follows Conventional Commits
  • Commits are signed off (DCO)

Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>
@matthewgrossman
matthewgrossman requested a review from a team as a code owner November 21, 2026 20:34
@github-actions github-actions Bot added the state:accepted A maintainer decided OpenShell should pursue this issue label Nov 21, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

state:accepted A maintainer decided OpenShell should pursue this issue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant