Update Available notification

[Michoels]

First of all, thanks for this fantastic CLI.
It has become absolutely critical to my daily work, great job!

I just noticed that I missed v3.0.2 and v3.0.3. I wasn't aware that they have been released.
It would be great if the CLI could print a notification New version v3.0.3 is available., or something similar.
(Probably powered by the project's public GitHub releases page).

Codex and NPM both have similar strategies.
It would be great if Fizzy CLI would have that as well.

Thanks so much!

[robzolkos]

@Michoels good idea! Will take it on.

[Michoels]

Thanks!
It might also be useful to have some way of keeping the installed skill file up-to-date - I noticed you made a bunch of updates to that too.
Maybe some sort of post upgrade message can notify that an upgraded skill file is available?

[joshyorko]

@Michoels you can brew install my downstream untill they get their build pipeline working take a look at code first of course to make sure you are cool but it should work on linux let me know if you want a macos binary as well and i can deliver. https://github.com/joshyorko/homebrew-tools/releases/tag/fizzy-cli-master-master.9a19631c2e5d

brew tap joshyorko/tools
brew install joshyorko/tools/fizzy-cli-master

it runs there latest of master which is a little experimental because they havent done a new release sense march and their brew command will fail immediatley.

mine will look for changes every day on master and rebuild from source.

[robzolkos]

Thanks again for the suggestion — this is a good idea, and I opened #175 to add it.

The notification follows the same general approach as the GitHub CLI: Fizzy checks the public GitHub releases page in interactive sessions, keeps machine-readable output clean, and throttles the check so it does not happen on every command. When an update is available, it will look like this:

A new release of fizzy is available: 3.0.2 → 3.0.3
Upgrade with your package manager, or download it from:
https://github.com/basecamp/fizzy-cli/releases/tag/v3.0.3

It can also be disabled with FIZZY_NO_UPDATE_NOTIFIER=1.

As of the next release, the installed skill is sourced from the installed CLI binary, not directly from the repo, so it stays in sync with the Fizzy version you have installed.