Repository navigation
v0.18.1
rness validateand the edit hook name a document ofadr/,specs/orplans/whose file name has no number, with the next one:plans/2026-10-02-x.md: not numbered; name it 0002-<slug>.md, the next number of plans. A plan another agent's skill wrote with a dated name is the usual case; rename it, or let the agent do it when the hook tells it. A workspace with such a file failsvalidate(and its CI) after the upgrade until it is renamed. The scaffold'sCONVENTIONS.mdstates the rule, andupgrademerges it in.- A dated file name is no longer read as a number:
rness doc newafter2026-10-02-x.mdgave2027, and two dated plans of one year were reported as one number twice. rness doc newracing another one at the same number says<file> exists; nothing written(exit 1) instead of a rawEEXIST.1 repository, not1 repositories, increateandsync.- When the SSH test passes only by asking for the key's passphrase,
create,addandsyncsay once how to load it into an agent (ssh-add), since every clone would ask again. - Ctrl+C while
createwaits for an organization's approval is a cancel in the plain look too:cancelled, nothing written, exit 0 (it was 130).
Full changelog: https://github.com/rness-dev/rness/blob/main/packages/cli/README.md
npm create rness # a new workspace
pnpm rness upgrade 0.18.1 # an existing one, from .rness/