Repository navigation
v5.4.0: cache, broker, scaling and verified upgrades
Every requirement traces to its evidence. Spec 109 (spec 109). Not breaking; no plugin changes. cplat spec trace <id> --chain [--json] is a new read-only view that follows each criterion through the tracked issue, spec, tests, reviewer verdict, merged PR, release and the tags pinned in dev, staging and prod, each link ok, missing, stale, unknown or n/a. Without --chain, trace is unchanged. It never writes, exits 0 whatever the states, and offline makes at most one 10 s gh attempt and marks what it could not read unknown. cplat spec ci now prints a warning (no change to the exit code) for each test that names a withdrawn or unknown criterion.
Fix rounds get a compact failure summary, not a raw log tail. Spec 108 (spec 108), ADR-071 (a failing check reaches an agent as a summary made by fixed rules, the full log stays on disk). Not breaking. A new package scripts/cplat/failsum summarises a failed check with one parser per template tool format (pytest, ruff, mypy, surefire, javac, go test, vitest, eslint, tsc, kustomize, kubeconform, docker build and more; anything else is format: unknown with the last 40 lines): own-code paths, repeated entries counted once, at most 20 entries and 80 lines, secrets redacted. cplat quiet, cplat validate run, the pre-push devbox run ci and the red CI checks of cplat component ship land and cplat pr wait print it, with the full log kept on disk next to a <log>.summary.json sidecar; spec 102's no-progress signature and recovery snapshot use the summary. Agent and brief instructions say to open the full log only when the summary is not enough. failure_summary: off in .platform-settings.yml or cplat quiet --raw restores the earlier output. A new benchmark workflow fix-rounds compares a build with summaries on and off.
Plugins: component 1.5.0, shared 1.1.0, svc 4.0.1, svc-go 0.4.1, svc-java 0.4.1, web 0.4.1.
The cache URL names its user, and CI pins its test tools. Spec 127 (spec 127). Not breaking. The url of an in-cluster cache is now redis://default:<password>@<host>:6379/0, so valkey-cli -u and client libraries take REDIS_URL as it is. A cache Secret that exists keeps its old redis://:<password>@... url (it is written once and authenticates as the same user default); new caches and new environments get the new form. /platform:update adds a url row per cache and environment to its change list. The platform's own test tools (pytest, pytest-xdist, pyyaml, ruamel.yaml) are pinned in requirements-test.txt, compiled from requirements-test.in; CI, scripts/ci-local.sh and devbox run test-fast install only from it, scripts/check-pins.py fails on a suite command that installs them otherwise, and a monthly grouped Dependabot pip entry moves them.
Unattended runs stop wasting turns and CI rounds. Spec 126 (spec 126), ADR-070 (the Stop hook holds only the owning session until it stops progressing). Not breaking. The Stop hook now holds only the session that started or resumed the run (the owner); other sessions are never held, and a run without an owner holds nobody and says so. The 8-stop limit is gone: two owner stops without a new commit or phase change escalate as no progress, with the last message as an excerpt and a cause chosen by a fixed rule (a matching escalation rule, else code on red evidence, else decision), so environment appears only with a matched rule. cplat component ship pr and cplat pr open check the title and, in the platform repo, the spec rule before devbox run ci and any push; --no-spec adds the no-spec label (platform repo only). devbox run ci in the platform repo runs the pr-title and spec-required checks locally through the same code as the CI jobs, and titles the platform builds are shortened to fit 72 characters and bytes. Action: resume runs that were open before the update once with /component:ship <NNN> (or /system:ship), so they get an owner.
Plugins: component 1.4.0, system 1.5.1.
The cluster-gitops validate gate checks the built manifests. devbox run validate (and quality, test, lint and the CI job quality) wrote the kustomize build to an extension-less temp file, which kubeconform skips, so the gate reported 0 resource found and passed without checking anything (#260). The build now goes to a .yaml file (#266), and the recipe fails when kubeconform checks 0 resources. Action: run /platform:update in each cluster repo; a repo with invalid manifests turns red.
Resources and environment properties upgrade safely. Spec 121 (spec 121), ADR-068 (resource and operator upgrades roll through the environments in verified steps) and ADR-069 (one versions table pins everything, and every release proves the upgrade). Not breaking: a system.yaml without the new keys renders as before, except that engine image references gain exact tags and digests (CloudNativePG publishes no plain tags for PostgreSQL, so they move to immutable build tags). Every image and chart the platform writes or installs is a row of one versions table (cplat platform versions [--diff <ref>] [--changelog]). /resource:upgrade <name> --to <major> [--env <env>] moves one environment per pull request, needs a backup from the last 60 minutes for a database, waits for health and runs the smoke tests; staging follows dev, prod is by hand. /platform:update keeps staging and prod on their held pins and prints the versions that change per environment, and cplat platform update --verify checks the operators once per cluster. The gitops repo answers property_operators: owner | install (existing repos keep owner; new ones get install, which renders External Secrets, Kyverno and LGTM). /platform:doctor --context [ENV=]CTX lists each operator as ok, missing, older or newer with its CRD versions, and /system:status gets a Resource versions section. A new end-to-end upgrade test and a release gate (scripts/release-check.py) prove every release upgrades from the previous one.
Plugins: resource 1.6.1 (/resource:upgrade; the cache url names default), platform 1.3.0 (doctor --context, update --verify), system 1.5.0 (status).
Versions (cplat platform versions --diff v5.3.0 --changelog):
postgres 1515.19 (digest none) → 15.19 (digest f617efc0)postgres 1616.15 (digest none) → 16.15 (digest 1ec419e9)postgres 1717.11 (digest none) → 17.11 (digest ed6923f9)postgres 1818.6 (digest none) → 18.6 (digest 39add80f)valkey 88.1.11 (new)valkey 99.1.3 (new)nats 2.142.14.9 (new)nats 2.152.15.2 (new)nats2.15.1 (new)seaweedfs4.51 (digest none) → 4.51 (digest f7a49e3f)opentelemetry-collector0.162.0 (digest none) → 0.162.0 (digest 39923a8e)lgtm0.35.0 (new)velero-plugin-for-awsv1.14.4 (digest none) → v1.14.4 (digest c85a7fa8)argo-cdv3.4.12 (new)k3sv1.32.5-k3s1 (new)gateway-apiv1.2.1 (new)operator nack0.35.0 (new)operator keda2.19.0 (new)operator metrics-server3.14.0 (new)
Action: run /platform:update in each repo. Optionally answer property_operators: install after removing a hand-installed External Secrets, Kyverno or LGTM.
Instances scale on load and queue depth. Spec 120 (spec 120), ADR-066 (instances scale with an HPA or KEDA, installed per cluster) and ADR-067 (Argo CD leaves autoscaled replica counts alone). Not breaking: a system.yaml without scale renders byte-identically. scale: {min, max, on} on a service or website component, or on one of its instances, follows one of four triggers: cpu, memory, a cache or a broker queue depth (lag). Only queue triggers may scale to zero; scale and replicas exclude each other. Argo CD ignores the replica count of a scaled workload through a RespectIgnoreDifferences rule. KEDA 2.19.0 and metrics-server 3.14.0 are installed as operators; the gitops repo answers resource_metrics: provided | install (default provided). The two "allowed:" key lists gain scale, and the e2e job limit is 90 minutes. /component:set --replicas refuses a scaled instance, /system:status shows replicas <n> (<min>–<max>), and /platform:doctor lists the KEDA and metrics rows.
Plugins: component 1.3.0, system 1.4.0, platform 1.2.0.
A message broker resource behind events APIs. Spec 119 (spec 119), ADR-065 (a broker is NATS with JetStream). Not breaking: a system.yaml without a broker renders as before. type: broker declares NATS with JetStream (version, replicas, storage, or external); an events API is bound with apis.<api>.broker, and its provider and consumers get NATS_URL, NATS_USER and NATS_PASSWORD from their own Secret, plus NATS_INBOX_PREFIX and EVENTS_<API>_* as literal values. NACK is installed as an operator to create streams and consumers. An unbound events API only gets a note. Pins: nats chart 2.15.1, nats:2.14.9-alpine, nats:2.15.2-alpine, nack chart 0.35.0 with controller 0.24.0.
Plugins: resource 1.5.0 (/resource:add <name> --type broker), api 1.1.0 (/api:list shows the broker of an events API).
A cache resource, compatible with Redis. Spec 118 (spec 118), ADR-064 (a cache is a platform-rendered Valkey StatefulSet). Not breaking: a system.yaml without a cache renders as before. type: cache declares a Redis-compatible cache (Valkey 8 or 9, memory, maxmemoryPolicy, optional persistence with storage, or external); a component that uses it gets REDIS_URL, REDIS_HOST, REDIS_PORT and REDIS_PASSWORD. No operator is installed, and cache data is not backed up. Pins: valkey/valkey:8.1.11, valkey/valkey:9.1.3.
Plugins: resource 1.4.0 (/resource:add <name> --type cache).