Skip to content

chore: publish the image to ghcr.io/ai-openshell/console and rename the Go module - #131

Merged
Gkrumbach07 merged 1 commit into
mainfrom
chore/ai-openshell-images
Nov 5, 2026
Merged

Gkrumbach07 merged 1 commit into
mainfrom
chore/ai-openshell-images

Conversation

@Gkrumbach07

Copy link
Copy Markdown
Contributor

Builds on #130 (repository links and chart path) and includes its commit. Merge #130 first, and this diff shrinks to its own commit.

What changes

The repository moved to ai-openshell/console. As agreed with Simon, the image moves with it, from the personal quay.io/gkrumbach07/openshell-dashboard to the org's GHCR.

  • Image registry. ci.yml and publish.yml build, push, retag and inspect ghcr.io/ai-openshell/console, signing in with the workflow's own GITHUB_TOKEN. The image jobs get packages: write (image-range gets packages: read and a login, because a new GHCR package is private). The QUAY_* secrets are no longer used.
  • Chart. dashboard.image defaults to ghcr.io / ai-openshell/console. global.image.registry stays quay.io, which is where oauth2-proxy comes from.
  • Image labels. Now io.github.ai-openshell.console.gateway.line and .sdk (Dockerfile, check-image-range.mjs, docs).
  • Go module. Now github.com/ai-openshell/console/backend. gofmt re-sorted the imports this moved and fixed an alignment in mock_sdk_test.go that was already on main.
  • Docs. Each image row says where it lives. Releases up to 0.1.3 stay on Quay, and the one-off gateway-0.0.116 image stays where it is.

Before the next release

  • An org admin has to make the console container package and the console/helm-chart/openshell-dashboard package public. Until then, pulls without a login fail.
  • Images 0.1.0–0.1.3 exist only on Quay. A chart installed with an old appVersion and these values would look for them on GHCR. Copy them over once with docker buildx imagetools create, or have Simon's mirror cover them.

Checks run locally

go build, go vet, go test ./..., node --test "scripts/**/*.test.mjs" (93 pass), the upstream Python tests (312 pass), gateway-range.mjs --check, helm lint, and helm template (renders ghcr.io/ai-openshell/console). Not run: helm unittest (plugin not installed here) and golangci-lint (the local build is older than Go 1.26).

🤖 Generated with Claude Code

@Gkrumbach07
Gkrumbach07 force-pushed the chore/ai-openshell-images branch from 011eb7f to ca9daaf Compare November 5, 2026 16:21
@danreed-rh danreed-rh self-assigned this Nov 5, 2026
@danreed-rh
danreed-rh self-requested a review November 5, 2026 18:10
danreed-rh
danreed-rh previously approved these changes Nov 5, 2026
…he Go module

The repository moved to ai-openshell/console, and the image moves with it
from the personal quay.io/gkrumbach07/openshell-dashboard to the org's GHCR.

- CI and publish.yml push, retag and inspect ghcr.io/ai-openshell/console,
  signing in with the workflow's GITHUB_TOKEN (packages: write on the image
  jobs), so the QUAY_* secrets are no longer used.
- The chart's default dashboard image is ghcr.io/ai-openshell/console; the
  shared registry stays quay.io for oauth2-proxy.
- The image labels are io.github.ai-openshell.console.{gateway.line,sdk}.
- The Go module is github.com/ai-openshell/console/backend (gofmt re-sorted
  the imports this moved, and fixed an alignment already on main).
- Docs say where each image lives: releases up to 0.1.3 stay on Quay, and the
  one-off gateway-0.0.116 image stays where it is.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Gage Krumbach <gkrumbac@redhat.com>
@Gkrumbach07
Gkrumbach07 dismissed danreed-rh’s stale review November 5, 2026 18:50

The merge-base changed after approval.

@Gkrumbach07
Gkrumbach07 force-pushed the chore/ai-openshell-images branch from ca9daaf to cba92ff Compare November 5, 2026 18:50
@Gkrumbach07
Gkrumbach07 enabled auto-merge (squash) November 5, 2026 18:52
@Gkrumbach07
Gkrumbach07 merged commit f74a274 into main Nov 5, 2026
15 checks passed
@Gkrumbach07
Gkrumbach07 deleted the chore/ai-openshell-images branch November 5, 2026 20:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants