On this page

Updates: choosing when your Wisent products change

Every Wisent product on your computer is updated by exactly one owner, and you choose how it behaves.

  • What Stado installed (stado product install, or the hourly stado product sync): Stado updates it, following your update rule below. A Mac app Stado built from source carries no update feed of its own, so it never updates itself behind Stado's back.
  • A Mac app you installed from a release (the .zip a release publishes): the app updates itself through its menu, Check for Updates…, with two switches: check automatically, install automatically.

Choose a rule

stado product policy set PRODUCT --mode automatic     # installs a newer revision by itself
stado product policy set PRODUCT --mode notify        # tells you, you install
stado product policy set PRODUCT --mode held --reason "why"   # never installs

Add --surface cli|desktop|service to choose for one part of a product only, --window 01:00-05:00 to let an automatic rule install only at night, and --channel stable (a CLI or service released by Stado) to install only promoted releases instead of building the latest source. stado product policy show prints every rule; stado product policy remove PRODUCT goes back to the default. The full rule, every field and every refusal: Keeping installed surfaces current.

See what is waiting, and install it

stado product available --json                 # what a notify rule left for you, with what it changes
stado product status --json                    # everything installed, its rule and what waits
stado product update PRODUCT                   # install one now
stado product update --all                     # install everything that waits (held ones stay held)

In a terminal, a Wisent CLI says once when a newer revision of it waits (… a newer revision … is waiting with N changes …). Stado Desktop's menu bar says how many updates wait and installs them after showing you the exact commands.

Stay on a version, skip one, take a security fix

stado product policy set PRODUCT --mode automatic --pin COMMIT     # stay on this revision
stado product policy set PRODUCT --mode automatic --unpin
stado product policy set PRODUCT --mode automatic --skip COMMIT    # never install this one
stado product policy set PRODUCT --mode held --reason "…" --security automatic   # but take security fixes

Go back

stado product rollback PRODUCT --surface SURFACE      # the installation before this one
stado product status PRODUCT --surface SURFACE --history --json   # every change: when, from what, by whom

An installation that fails its readiness check after a sync is rolled back by itself, and that revision is not installed again until a newer one is published.

While you work

An open desktop application is not replaced under you: sync waits until you quit it. After a CLI update, stado product status PRODUCT --surface cli --json lists under restart_needed the processes still running the old program.

Source: this website