tiennm99/ccs
1
0
Fork 0
mirror of https://github.com/tiennm99/ccs.git synced 2026-07-20 04:17:37 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(ci): clarify rc.1 soak and :full removal as intentional design (#1261) (#1279)

Browse Source 
Reviewer kept flagging :full omission and stale :latest as bugs. Both are intentional per Q3 maintainer decision and the rc.1 soak design (loop-5). Strengthen inline comments to make this unmistakable to future readers.
This commit is contained in:
Kai (Tam Nhu) Tran
2026-05-17 06:13:55 -04:00
committed by GitHub
parent e7ce699dc2
commit d2f7d3f407
2 changed files with 20 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/workflows/docker-release.yml
+13 -4
View File
@@ -400,10 +400,19 @@ jobs:
# --------------------------------------------------------------------------- # ---------------------------------------------------------------------------
# Job 4: Promote mutable tags — runs ONLY after smoke tests pass # Job 4: Promote mutable tags — runs ONLY after smoke tests pass
# Adds :latest, :<major>, :<minor> aliases pointing to the immutable digest. # Adds :latest, :<major>, :<minor> aliases pointing to the immutable digest.
# Never triggered automatically by release events — requires an explicit #
# workflow_dispatch with promote_to_latest=true (via promote-release.yml or # INTENTIONAL DESIGN (issue #1251 rc.1 soak — see docs/release-process.md):
# direct gh CLI call) after the operator confirms the immutable :<ver> image # GitHub release events publish ONLY the immutable :<ver> tag. The mutable
# is stable. This is the sole rc.1 soak gate for Docker mutable tags. # :latest / :<major> / :<minor> aliases STAY POINTED AT THE PRIOR STABLE
# RELEASE until an operator manually promotes after a soak window (~24h).
# Trade-off: zero-install users (curl ccs.kaitran.ca/docker-compose.yaml &&
# docker compose up -d) keep receiving last-known-good :latest during the
# soak; operators wanting the new version pull :<ver> directly.
#
# Operator promotion:
# gh workflow run promote-release.yml -f tag=v<X.Y.Z>
# (or equivalently: gh workflow run "Publish Docker Image" -f tag=v<X.Y.Z>
# -f promote_to_latest=true)
# --------------------------------------------------------------------------- # ---------------------------------------------------------------------------
promote-mutable-tags: promote-mutable-tags:
name: Promote mutable tags (:latest / major / minor) name: Promote mutable tags (:latest / major / minor)
docker/Dockerfile.integrated
+7 -3
View File
@@ -3,9 +3,13 @@ FROM eceasy/cli-proxy-api:latest
ARG CCS_NPM_VERSION=latest ARG CCS_NPM_VERSION=latest
# CCS integrated image: CCS CLI + CLIProxy + supervisord. # CCS integrated image: CCS CLI + CLIProxy + supervisord.
# No AI CLIs (claude-code, gemini-cli, etc.) are bundled. # Design choice (issue #1251 final scope): single-image strategy. The originally-
# To use AI CLIs alongside CLIProxy, run them in sibling containers # proposed `:full` variant bundling claude-code/gemini-cli/grok-cli/opencode was
# attached to ccs-net — see docker/README.md#connect-your-app-to-cliproxy. # DROPPED on maintainer review. Rationale: smaller surface area, fewer supply-
# chain dependencies, simpler tag taxonomy. Users needing AI CLIs run them in
# sibling containers attached to ccs-net — the public DNS contract guarantees
# http://ccs:8317 reachability. See docker/README.md#connect-your-app-to-
# cliproxy. Historical record: CHANGELOG.md "### Removed" entry.
RUN apk add --no-cache \ RUN apk add --no-cache \
curl \ curl \