Skip to content

v5.23.3

Latest

Choose a tag to compare

@ika100 ika100 released this 16 Nov 18:21
· 31 commits to main since this release
8c10675

Fixed

A session that waits for a cplat command no longer loops on model calls (#750). The Stop hook blocked the stop of a session while its wait ran, and every block made the session answer with another model call; a 60 s wait could cost dozens of calls. Now the session may stop and the hook counts nothing. Under cplat headless the wait runs detached, no next session starts until it ends (polling local files, no model call), and the next session is told the result at its start. A loop guard stops a session that makes calls model calls without progress in minutes minutes and escalates with looping: ...: --loop-guard <calls>/<minutes> (default 10/5), guard.loop_calls (3 to 100) and guard.loop_minutes (1 to 60) in .platform/dispatch.yml. cplat dispatch pause now reaches running units at their next stop, status shows paused_at and the units escalated today, and cplat needs names the cause of an escalation (ADR-115). Update the plugins (/plugin marketplace update).

cplat next reads all its sources within its 20 s limit again (#782). In journey 20 its run records and GitHub sources timed out on every call, so the hand-over guide never showed the next step. The run store now asks its days in parallel, and one next, status or needs call reads each day once for all its readers. Only the system's own runs get rows and PR lookups, and the GitHub sources are asked at once: on the journey's system next takes about 10 s with every source read, where before it hit 20 s with two sources missing. Releases show again (gh release list has no url field). Update the plugins (/plugin marketplace update).

cplat pr wait --merge no longer merges before a pull request's CI run exists (#787). GitHub creates the pull_request workflow runs a few seconds after a push, while CodeQL's checks may already have passed. A wait that polled in that gap saw only green CodeQL checks and merged; two platform PRs reached main with their CI red. Now, in a repo whose workflows run on pull requests, a head is green only once such a run exists on it, and if none appears within 5 minutes the wait ends with an error instead of a merge.