Skip to content

Releases

Kito 0.39.1

Choose a tag to compare

@github-actions github-actions released this 22 Nov 18:45

The first release since 0.38.0: it carries 0.39.0 too (plugins of a
server that work on their own, git_sync), which CHANGELOG.md describes.

  • A way to sign in that is not set up is said so. The server asks
    each sign-in plugin sign-in ready when it lists them, and /-/sign-in
    carries ready (and why): a client does not offer one that could
    only fail. A plugin that does not know the question is taken to be
    ready.

Kito 0.38.0

Choose a tag to compare

@github-actions github-actions released this 22 Nov 14:38

A review sent whole (ADR 0019).

  • submit_review: the comments of a review and its verdict in one
    go, every comment checked before any is written; the agent is told
    them together. A request for changes that stands is told to the agent
    too.
  • Suggested changes: a comment on lines carries the lines to put in
    their place; the agent is told them, and apply_suggestion writes them
    into the lane and resolves the comment.
  • What changed since my review: a verdict keeps what the files were;
    changes_since_review shows what changed since, against that.

Kito 0.37.0

Choose a tag to compare

@github-actions github-actions released this 22 Nov 13:59
  • The command line has Kito's look: kito --help starts with the
    logo (three lanes that become one line, ending in a dot), the name and
    the version, and lists the commands in groups, the most used first
    (start, lanes, history, assistants and plugins, git, server, settings).
    Headings are in Kito's indigo; commands and flags in bold; lane and
    checkpoint names, what went in, notes and the kito: of errors are
    coloured too. Colour is only for a terminal: none when the output goes
    to a file or a program, with NO_COLOR, with TERM=dumb, or with
    --json; CLICOLOR_FORCE=1 asks for it anyway (D-174).
  • Help lines are shorter: the first sentence is shown with -h, the rest
    with --help. kito hook is for assistants, and is no longer listed.
  • kito claude is gone: kito assistant add claude does the same.

Kito 0.36.0

Choose a tag to compare

@github-actions github-actions released this 22 Nov 12:44

Repositories from afar (phase 35,
ADR 0018).

  • kito repos add for admins in a connected directory: an empty
    repository, one cloned from a git address (a token used once and kept
    nowhere), or one sent from this machine with --push: a Kito
    repository with all its history, or a git one.
  • kito repos archive: out of use, deleted after 30 days; owners
    unarchive or delete it now. kito repos rename: directories
    connected with the old name still reach it.
  • The same on the server's machine: kito-server repo archive | unarchive | delete | rename.

Kito 0.16.0

Choose a tag to compare

@github-actions github-actions released this 20 Nov 16:11

Permanent lanes (ADR 0001).

  • kito lane create staging: a lane next to main that is never closed,
    named wherever a lane is named (--on staging, kito integrate staging).
  • Landing on a permanent lane makes a checkpoint of it, runs its checks
    ([lanes.<name>] verify), and exports it to its own git branch, pushed
    with main's.
  • kito integrate staging lands it on main as a git merge; it stays open.
  • kito lane catch-up staging brings in what landed on main directly.
  • [lanes.<name>] integrate: who may land on it.
  • The store's format becomes kito-store 3 once a permanent lane or a lane
    on a lane exists; older versions refuse it.
  • Fixes: Kito asked rust-analyzer before it had loaded the project, between
    two of its phases of work, and could find no use of a function; it now
    waits until rust-analyzer says it is done. A file with syntax errors could
    be read differently depending on its previous version; it is now read
    from scratch.
  • Tested on macOS in CI for the first time. Known limit there: a save that
    a program writes slowly, in several steps, may be recorded half-way, then
    again when complete. Linux knows a file is complete when it is closed
    after writing; macOS's file events do not say so. Editors that save
    quickly or by renaming a new file into place are not affected.