ShvIA
TIMELINE
SIGN IN

ShvIA Desktop

Version — · manifest generated —

  • — the published version, read from the manifest
  • — platforms only what has actually been published
  • auto-update install once — the app updates itself from this same manifest
  • sha256 on every file, to check what you downloaded

Every published file

One row per artifact, with the size and the full sha256 the manifest declares. Nothing here is estimated — if the manifest cannot be read, the list stays empty and says why, because a made-up version number is worse than no list.

Availability by system

Your system is not in the list? Available installers are the ones in the release manifest above. If a platform is not listed, this channel has no installer for that platform in this version.

Checking what you downloaded

Every file carries a sha256 in the manifest. Compare it against the file you got:

terminal — checksum 
# Linux — paste the filename from the row above
$ sha256sum FILE
# macOS
$ shasum -a 256 FILE

Some rows are also marked signed: those carry a minisign signature, which is what the updater itself verifies before installing an update. The rows marked sha256 only are the ones the updater does not consume — for those, the checksum is the check.

Where this comes from

The desktop client is a native window over the same ShvIA the browser serves, and it carries the anna CLI inside the installer. It updates itself: you install once, and the app pulls later versions from the very manifest that filled this page. That is why this list cannot fall behind what the app trusts — there is only one file, and both read it.