Skip to content

ci(release): promote release images to Quay - #5807

Draft
SDAChess wants to merge 1 commit into
mainfrom
ci/4554-publish-releases-to-quay/SDAChess
Draft

SDAChess wants to merge 1 commit into
mainfrom
ci/4554-publish-releases-to-quay/SDAChess

Conversation

@SDAChess

Copy link
Copy Markdown
Contributor

Summary

Releases stop publishing to ghcr.io/nvidia/openshell, which is frozen after the move to ai-openshell/openshell. Release Dev and Publish Release now copy the SHA-tagged CI images to quay.io/ai-openshell/{gateway,sandbox,supervisor}, logging in with the job's OIDC token and no stored secret.

Draft until the repository has moved to ai-openshell and the release environment exists. Before that, the Quay login has no valid OIDC subject to match.

Related Issue

Refs #4554

Changes

  • Release Dev: copies ghcr.io/${GITHUB_REPOSITORY_OWNER,,}/openshell/<component>:<sha> to Quay as both :<sha> and :dev. The :<sha> tag backs the 0.0.0-dev.<sha> chart, whose appVersion is that SHA.
  • Prereleases: copy the CI image's SHA tag to quay.io/ai-openshell/<component>:<version>.
  • Stable releases: push the image archives straight to Quay, keeping the never-overwrite guard. latest is retagged within Quay.
  • SBOM checks: run verify-image-sbom.sh --require-cargo against the Quay tag users pull, for dev, prerelease and stable.
  • Login and permissions: both promotion jobs run in environment: release with id-token: write, and packages drops to read, which is enough to read the CI registry. They log in through ai-openshell/workflows/quay-login, pinned to the commit ai-openshell/console uses, as ai-openshell+openshell_release.
  • Job IDs: tag-ghcr-dev and tag-ghcr-release keep their IDs; only their display names change. This keeps the needs lists and the publication check unchanged, and keeps the diff to promotion and login lines so it rebases cleanly with the runner changes.

Setup this needs (outside the repo)

  • Quay robot ai-openshell+openshell_release with Write on gateway, sandbox, supervisor, charts/openshell and charts/openshell-workspace.
  • Federation: issuer https://token.actions.githubusercontent.com, expected subject repo:ai-openshell@311201172/openshell@1166129534:environment:release. This is the ID-based format measured on a test repo transferred into ai-openshell. Confirm it from a real run once this repository has moved.
  • GitHub environment release with no required reviewers, because Release Dev runs on every push to main. Its deployment policy has to admit main, release/* and v* tags.

Testing

  • Cross-registry copy: I copied the published ghcr.io/nvidia/openshell/gateway:dev to a local registry with the same docker buildx imagetools create --prefer-index=false command. The copy has the same index digest, keeps provenance for linux/amd64 and linux/arm64, and passes tasks/scripts/verify-image-sbom.sh --require-cargo (SPDX=2, Cargo=1027).

  • Overwrite guard: against the empty Quay repo, skopeo inspect returns manifest unknown, which is what the stable guard checks for.

  • Lints: actionlint passes on the changed workflows, and zizmor reports no findings that aren't already on main.

  • Not verified: the Quay OIDC exchange, and whether Quay accepts the attestation manifests on push. Both need the moved repository; a dev release after the transfer covers them.

  • Checks appropriate to the affected code and behavior pass

  • Unit tests added/updated (if applicable)

  • E2E tests added/updated (if applicable)

Checklist

  • Follows Conventional Commits
  • Commits are signed off (DCO)
  • Architecture docs updated (if applicable)

Release Dev and Publish Release now copy the SHA-tagged images from the
CI registry (ghcr.io/<owner>/openshell) to quay.io/ai-openshell instead of
retagging them in ghcr.io/nvidia/openshell. Stable archives are pushed to
Quay directly. Jobs log in to Quay through the org's quay-login action
with the job's OIDC token, so they run in the release environment.

Dev also pushes the SHA tag so the 0.0.0-dev.<sha> chart resolves, and
dev and prerelease promotions verify the SBOM on the Quay copy.

Refs #4554

Signed-off-by: Simon Scatton <sscatton@nvidia.com>
@copy-pr-bot

copy-pr-bot Bot commented Nov 20, 2026

Copy link
Copy Markdown

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

@github-actions github-actions Bot added the state:accepted A maintainer decided OpenShell should pursue this issue label Nov 20, 2026
@github-actions

Copy link
Copy Markdown

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