Repository navigation
v0.10.2
Fixed
use,syncandpruneno longer print a bareok <app>line for an app that was already
in sync. An empty change list was rendered as nothing at all, leaving a row of trailing
whitespace that read as a truncated or failed result; it now saysunchanged, which is what
a repeatedsyncactually did.- Codex states the Responses requirement only when the endpoint has not declared itself
Responses-compatible. The caveat was printed unconditionally, so a provider the user had
already markedresponses— where there is nothing to warn about — warned anyway, and a
fully successful sync looked like it had a problem. - Syncing to a machine whose agent configs do not exist yet no longer prints a
backup: …line
when nothing was backed up. A transaction directory was created for every commit even when
every planned file was new, so on a first run the output announced eight backups that held
nothing but a manifest.
Full Changelog: v0.10.1...v0.10.2