kunobi-ninja/kache v2.0.0-rc.2

v2.0.0-rc.2: scriptable config, shell completions, compact monitor

on GitHub

Configure projects from scripts with the new kache config subcommands. kache init now installs shell completions, and the monitor keeps selected build details readable in small terminals. Long compiler invocations stay cacheable on Windows, and upgrades can replace a running 1.x daemon.

cargo binstall kache --version 2.0.0-rc.2
kache init

Added

• Config: Read and edit explicit file values with kache config get, set, unset, list, and path. Select --project, --global, or --file; all five commands support JSON. Edits preserve comments and use an atomic replacement under a writer lock. #1732 by @jleni.
• Setup: kache init installs and refreshes Bash, Zsh, and Fish completions on Unix. Preview with --check or skip shell changes with --no-shell. #1723 by @jleni.
• Diagnostics: kache explain --all lists every retained skip and passthrough, including archived events, with root filtering and JSON output. kache doctor shows volume identity and available inode counts. #1722, #1727 by @jleni.

Changed

• Monitor: Selecting a build shows its summary, events, and miss causes on the Now tab. Narrow terminals stack the selector above the details; short terminals retain a compact summary. #1724 by @jleni.

Fixed

• Windows: Compiler arguments move into a response file when Kache's added flags would overflow the Windows command line. This keeps affected builds cacheable. #1717 by @TastyCZ and @jleni.
• Daemon upgrades: Compiler invocations can replace an incompatible running daemon, and kache init waits for the new daemon to become ready. Existing services using the matching frontend remain valid. #1718 by @jleni.
• Windows delegation: Both peers can opt into trust_daemon_execution to accept known process-identity token differences. Unknown attributes still fall back to local execution. #1730 by @jleni.
• Workspace replies: Slow cache restores no longer close the Unix broker after five seconds. Requests remain cancellable while waiting for a reply. #1733 by @jleni.

When upgrading from 1.x, install matching kache and kache-engine binaries. Managed incremental state starts cold once. See the upgrade instructions.

Contributors

Full changelog: v2.0.0-rc.1...v2.0.0-rc.2