Skip to content

v5.18.0

Choose a tag to compare

@ika100 ika100 released this 12 Nov 08:21
· 120 commits to main since this release
b4d184a

Added

Container logs now reach the log backend (#182). Until now logs arrived only if a service's SDK pushed them. With observability on, the environment's collector pod runs a log-tailer container that follows every pod's stdout through the Kubernetes API (a namespaced Role for pods and pod logs; no ClusterRole, DaemonSet or host path, so the Kyverno guard rails still admit every workload) and sends it to the collector with service_name, k8s_namespace_name, k8s_pod_name and deployment_environment. The component templates log trace_id and span_id so a log line links to its trace. See ADR-098. Run /platform:update to pick it up in existing environments.

Shared numbers and indexes now come from cplat (#659, #660, #477, #577). cplat spec new takes one more than the highest spec number on main, every pushed branch and every open PR, and cplat spec check reports a spec or ADR number that this branch and another branch or PR both add. cplat adr add <slug> --decision "<one line>" writes the next ADR from the platform's template and appends exactly one row to the ADR index, so the architect no longer numbers ADRs or edits the index by hand. A criterion that changes another spec's active criterion ends with (replaces AC-<NNN>.<n>); the old one is struck through as superseded by, counts as withdrawn in trace, verify and the done count, and cplat spec check refuses an unstruck target (cplat spec new --from-plan strikes it for a system plan's slice). A cplat command whose output pipe is closed (cplat … | head -1) exits 141 without a traceback and no longer files a crash issue. See ADR-099 and spec 183. Update the plugins (/plugin marketplace update).

Parallel ships no longer stop each other, and the usage limit pauses a run instead of failing it (#184). Runs in several worktrees used to collide on one ship slot, a usage limit ended a run as a failure, and a land stopped when another PR took the same ADR number or rule number. Now cplat headless takes a slot from a per-repo pool (slots in .platform/dispatch.yml, shared with the dispatcher and every worktree), prints waiting for a slot: held by … or, with --no-wait, exits 1 with slot busy: held by …, and frees a stale slot with freed a stale slot of …. A session that hits the usage limit pauses the run (paused: usage limit, next try at <time>, 5 to 60 minutes between tries) and after 360 minutes in total exits 1 with environment pause: usage limit resets at <time or "unknown">, recorded as escalated with cause environment; running the same command again continues. The land renumbers a clashing ADR and rule register entry (renumbered ADR-<old> to ADR-<n> …) and reads CI logs on its allowlist. devbox run ci lints changed templates and reports file, line and rule, and env-prefixed devbox commands in a plan are allowed verbatim. See the guide. Update the plugins (/plugin marketplace update).

A guide to reviewing a spec before you approve it (#661). Approval is the one decision the platform cannot take for you, but nothing said what to check in it. The new guide Reviewing a spec gives a reading order that lets you stop at the first wrong part, one question per part, and red flags for acceptance criteria, including a criterion that changes what an earlier spec promised (#477). The quickstart links to it at the approval step.

Changed

Unattended runs ask less: instance settings, git rm, type-only test changes, one test review and smoke findings no longer stop for you, and platform-repo escalations go to the desktop (spec 179). Instance settings from the system plan become before-merge gitops entry operations (#653), git rm of tracked files is allowed (never forced, #654), type-only test changes are recorded with --tighten (#655), the acceptance tests are reviewed once before they freeze (ADR-101), the tester fixes smoke-test findings in the build (#616), and escalations of runs in the platform repo go to the desktop, never to GitHub, unless events.escalation.github is set (#642, #643). Action: update the plugins (/plugin marketplace update); gitops-app repos get the new plan check with /platform:update.

The journey measurement counts the system ship's repo sessions as agent time and attributes waiting only from evidence (spec 181). The old scripts/journey/measure.py counted a minute as waiting whenever the coordinator waited, even while a headless repo session worked, and named the kind of wait from the command text alone. The measurement is now cplat platform runs journey measure (scripts/journey/measure.py forwards to it): each minute counts once, a person first, then agents when any thread works (the coordinator, its subagents, and the repo sessions found through the run records), then waiting. Waiting is attributed to CI, deploy, promotion, restore, cluster or smoke only from evidence (Actions runs, run-store phases, wait records), otherwise it is unattributed. --steps prints a per-step table, --json the exact split, and --journey <run_id> writes it to the journey record as a journey_split follow-up that cplat platform runs report --benchmarks shows as medians per stage, part and journey. See ADR-096 and spec 181.

Fixed

Every merge into main takes one land path with a stated mode (#648). A release whose branch fell behind main used to catch up silently; it now pushes and merges nothing and stops with main moved: start the release again and a fix: line (close the release PR, delete the release branch, run cplat platform release). The other land commands update the branch and wait for the new head's checks before merging, and a refused merge goes back to waiting, at most 3 times, then stops with merge refused 3 times: <reason>. Tests in tests/cplat wait for events through tests/cplat/waiting.py instead of fixed sleeps, and scripts/check-test-sleeps.py checks it (ADR-100, ADR-097).