Repository navigation
Pendulum 0.10.5
Pendulum 0.10.5
- Re-check a usage-limit hold whose reset is far off, and release it once the account answers (#613) (#615)
- Report: a --self login is trusted only on a positive answer (#607) (#612)
- Count the card's and the report's records only from verified writers (#607) (#610)
- Progress card while running: a run's cost at its end, no ended Now row, rows in time order, reruns stay live (#611)
Upgrading from v0.10.4
- Re-pin to
clockgrove/pendulum@v0.10.5. The workflow template is unchanged. - Finish cards and
pendulum reportcount stage, spend and decision records only from authors whose write access is verified (#607). A read-only member's markers count nothing. In the report, an author whose permission the call budget didn't reach, or GitHub refused, givesauthor-uncheckedorauthor-unverifiableinsource.missing, and their records are unknown cost, never dollars. pendulum report --self: a login is listed insource.trusted.loginsonly once it is decided a writer. Otherwise it is listed insource.trusted.refusedwith a reason:cannot-push,unverifiable,uncheckedorno-record.- Local mode: while a usage-limit hold's reset is more than an hour away,
servere-probes the held account about every 30 minutes with one tiny call, and releases the hold when a model the limit applies to answers (#613). The probe's cost is in serve's log.
Fixed
- #608, the live progress card:
- a run's cost shows in the headline and its row as soon as the run ends;
- a step that has ended is never the Now row, and there is none between steps;
- rows are in time order with Now last;
- a rerun pass shows its own Now row;
- every write goes through one queue, so the exit write is always last.
Release check
Claude and Copilot passed end to end on Actions, on pendulum-scratch:
- the live progress card was read through 33 written states, and all checks held;
- the finish card and the report agree;
- the repo owner is trusted;
- every stage records the candidate build.
Known limits
- A card's
passes.totalcounts decision records, while the report counts them apart (decisionRecords). A stage with AI judge calls shows one more pass on the card.