v0.1.18 — tacet update just updates

tacet update now does what the word says

Before this, tacet update told you a newer version existed and did nothing; you then typed tacet update --install to get what the first word had already promised. That is the most ordinary kind of trap — the command that sounds like the whole job doing half of it — and it was reported the moment someone hit it.

tacet update           # checks, asks, installs
tacet update --check   # looks only, writes nothing

--install still parses, so older instructions and muscle memory keep working.

The consent did not change. The download still names the file, its size and its computed digest, and still asks before replacing anything:

  to download: tacet-aarch64-apple-darwin  (14.4 MiB)
    source: https://github.com/farukciftler/tacet-cli/releases/download/...
    target: /Users/you/.cargo/bin/tacet.new
  Download it? [y/N]

"Update" is the default intent, never a silent action. --no-approval remains the only way past that question.

Being up to date is no longer an error

It was returned as one — harmless while installing needed its own flag, and not harmless once the bare command installs, because the most common run of all would have printed a yellow failure and exited non-zero. It prints one line and exits zero:

  already on the newest release (0.1.18)

Also

The argument table now has the test clap only performs on request, so a conflicting flag or a bad default fails the build instead of the first user.

Crates

tacet-cli 0.1.18

cargo install tacet-cli --features candle

Full Changelog: v0.1.17...v0.1.18