Repository navigation
v0.18.0
- The published CLI runs on Node 22.17 or later (ADR 0010); the guard compares major and minor. A workspace pinned to 0.17.x keeps refusing Node 22 until its pin moves: from inside it,
npx @rness/cli@latest upgradeworks under Node 22, sinceupgradeis served by the copy invoked, never the pinned one. rness createasks where the organization lives first — the blank workspace is that question's last answer — then offers the login, which now lists the organizations you belong to that have approved rness (your account last, thenan organization not listed here…for the rest). Right after the organization and before anything reads it, an organization that restricts OAuth apps and has not approved "Rness" gets its approval page opened in your browser; the wizard waits for the owner's click (10 minutes at most) and then lists the private repositories too. See "GitHub login"./rness:adr,/rness:specand/rness:planread their first word as the verb:create,open(a bare number), and for a planfrom <spec>— which approves the specification it plans — andcheck NNNN, the proofs of a plan, in place of/rness:done./rness:doneis retired:rness syncremoves itsSKILL.mdwhere an earlier release wrote it (removedin its output); commit the deletion in each repository, asupgrade's next steps list. Note:/rness:plan 0028now opens plan 0028; a plan is made withfrom <spec>. See "Agent targets".rness doc new <collection> [--title <text>]writes the next numbered document ofadr,specsorplansand prints its path: the skills allocate with it instead of counting.rness validateand the edit hook refuse two documents with one number in a collection.- The day of a release,
pnpm create rnessruns the previous version: pnpm ≥ 11 holds back a package younger than 24 hours (minimumReleaseAge).rness upgradeinstalls the latest all the same.
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.0 # an existing one, from .rness/