Keep TOVIO up to date

Read this before assuming either product updates itself. Neither does yet.

Nothing checks for updates today

The desktop app does not check for updates, and there is no setting to turn off, because nothing is running. The updater plugin is compiled in and the release configuration is complete, but no code path in the app or its interface ever calls it, and the app's browser layer is granted no updater capability, so it could not reach one if it tried.

Both the desktop status ledger and the package's own follow-on list still record the signed auto-updater as open work. It is a stated gap, not a silent one.

So what is built

The root of trust and the release plumbing, which are the hard parts:

• A minisign public key is baked into the shipped binary. An update whose signature does not verify against that embedded key is rejected — the app never falls back to installing it anyway.
• The private half is generated offline by the owner, never by CI — a root of trust minted by a build runner would be a root of trust held by everyone with workflow access.
• The release job that produces the update manifest fails closed when a platform's signature is missing or empty, on the grounds that a manifest entry without a valid signature is worse than no entry: every client would download the payload and then reject it.
• The manifest is served from the project's own release assets, and its timestamp comes from the tagged commit rather than the clock, so re-running the job over the same artifacts produces the same bytes.

What an update check would send

When checking does land, it will do one thing: ask whether a newer version exists. It will not report your repositories, paths, identity, or usage. TOVIO's governance rule is that the software does not report to anyone unless you act, and an update check is the narrow, user-visible exception rather than a telemetry channel.

Until then the honest statement is stronger: the desktop app's interface is under a content-security policy that permits no outbound network connection at all. It talks to its own local engine and to nothing else.

Updating today

• Desktop: download or build the newer version and install it over the old one.
• CLI built from source: pull and rebuild. It has never updated itself and does not pretend to.
• Editor extensions: rebuild the .vsix or the plugin zip and reinstall. Neither is published to a marketplace, so neither receives marketplace updates.

Read the changelog first

TOVIO is pre-1.0 and a release can change behaviour you depend on. The changelog is the system of record for what changed — and with no update notifications, it is also the only way you will hear about a security fix.

After a CLI upgrade

Regenerate your shell completions. They are produced from the command surface of the version that generated them, so an old completion file will happily offer you flags that no longer exist.