snare 1.9.0 — update restarts the guard, notifies or auto-installs

snare update now restarts the guard and cleans up after itself. And snare tells you when there's a new version, or installs it for you.

No more snare guard stop && snare guard start

After an update, the background guard used to keep running the old version until you restarted it by hand. snare update now restarts it on the new code. It also catches a guard that is still on an older version even when there's nothing new to download. To do it yourself any time: snare guard restart.

Old leftovers are cleared

An update now removes what the previous version left behind:

• the gate's cached verdicts, which only the old version could use;
• blocks waiting in snare respond for repositories you've since deleted;
• the oldest part of any log past 1 MB.

Your backups, reports and evidence are never touched.

Told when there's a new version, or updated automatically

Choose how snare keeps itself current:

snare update --mode notify   # the default: tells you when a new version is out
snare update --mode auto     # installs new versions itself, then tells you what changed
snare update --mode off      # never checks

• notify checks in the background, at most every six hours, and shows one line: snare 1.9.1 is out (you have 1.9.0) — update: snare update.
• auto only moves forward along main and never touches an install you've edited. It logs to ~/.snare/logs/auto-update.log.
• The check now also runs when a coding agent is using snare. Before, it only ran in a terminal, so installs used mostly through agents never found out about new versions.

Update

snare update && snare selftest

This one time, the update runs on your current version, which doesn't know how to restart the guard yet. So restart it yourself once: snare guard stop && snare guard start. From 1.9.0 on, snare update does it for you.

136 self-test checks pass.