snare 1.7.1 — the 'behind' message goes away after you update

The "commit(s) behind" message now goes away after you update.

snare remembers whether it's behind so it doesn't need to ask GitHub on every command. But it never updated that memory when you updated. Right after snare update succeeded, every command still said "1 commit(s) behind, run: snare update". The memory refreshed only once a day, and only in an interactive terminal. Under a coding agent it never refreshed at all. One install showed a "behind" from 19 days and three releases ago.

Now the memory is tied to the exact commit it describes. As soon as your install changes, it's ignored, whether that's through snare update, a git pull or a reinstall. snare update records the result it just reached.

Together with 1.7.0, which makes snare update always update from main, this fixes "snare says it's up to date but I'm stuck" and "snare says I'm behind but update does nothing".

Update

snare update && snare selftest

On a version before 1.7.0 and stuck? Run this once:

cd ~/snare && git checkout main && snare update

131 self-test checks pass.