Cut a ServiceRadar release and roll the Kubernetes `demo` namespace to the resulting published semver image tag through ArgoCD Image Updater. Use when the user asks to update `VERSION` and `CHANGELOG`, run `scripts/cut-release.sh`, push the release refs, wait for published release artifacts, and then refresh `demo` to that released version. Do not use for pre-release local testing with unpublished images; use `$demo-local-rollout` or `$demo-web-ng-fastpath` for that. Use when this capability is needed.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Cut a ServiceRadar release and roll the Kubernetes `demo` namespace to the resulting published semver image tag through ArgoCD Image Updater. Use when the user asks to update `VERSION` and `CHANGELOG`, run `scripts/cut-release.sh`, push the release refs, wait for published release artifacts, and then refresh `demo` to that released version. Do not use for pre-release local testing with unpublished images; use `$demo-local-rollout` or `$demo-web-ng-fastpath` for that. Use when this capability is needed.
metadata
{"author":"carverauto"}
Release Cut And Demo Roll
Overview
Use this skill for the formal release path: update release metadata, cut the release commit and tag, publish the refs, confirm that the release artifacts exist, and then roll demo to the released semver image tag, such as v1.2.41. Prefer the repo's existing release script, CI publish path, and ArgoCD Image Updater over ad hoc local image pushes.
Workflow
Work from the repo root on the intended release branch.
Update VERSION and the top CHANGELOG entry for the new semver.
Dry-run the release cut to verify the changelog entry is wired correctly.
Run scripts/cut-release.sh --version <version> and append --push when ready to publish refs.
Confirm the release commit and tag landed where expected.
Wait for the published release artifacts to exist for the target semver tag.
Let ArgoCD Image Updater advance demo to v<version>, or patch the Argo app to v<version> if an immediate manual reconcile is required.
Watch Argo until demo reaches Synced|Healthy|Succeeded.
Report the release version, release commit, release tag, Image Updater status, and final demo rollout status.
Guardrails
Use this only for actual release cuts. Do not use it for one-off local testing or unpublished commits.
Do not bypass scripts/cut-release.sh unless the user explicitly asks for a different path.
Do not treat the release as deployable until the published artifacts for the release version actually exist.
Prefer published release artifacts over rebuilding images locally in this workflow.
Roll formal releases with the semver image tag, for example v1.2.41. The sha-<commit> path is for unpublished local demo testing only.
Do not switch ArgoCD Image Updater back to newest-build over sha-* tags. Harbor tag timestamps can point demo at an older release; semver policy avoids that failure mode.
When the user wants the refs published immediately, use:
scripts/cut-release.sh --version <version> --push
Afterward, capture:
git rev-parse HEAD
git describe --tags --exact-match
Keep the release commit SHA for reporting and traceability. Use the release version as the demo image tag source: v<version>.
Published Artifact Expectations
Do not roll demo until the release artifacts for the target semver tag exist.
Typical release build path from this repo:
./scripts/docker-login.sh
bazel build --config=remote $(bazel query 'kind(oci_image, //docker/images:*)')
make push_all_release
In practice, this usually runs in CI instead of locally. The important requirement is that the release images for the target version are published and signed before the demo rollout starts.
If only a single release image must be republished, use the matching Bazel push target. If only Wasm plugins are relevant, use make push_wasm_plugins.
Roll Demo To The Release Tag
The steady-state demo path is ArgoCD Image Updater with a semver strategy. After the release images are published, force a reconcile if needed:
