Skip to main content
bach feed writes the small JSON file an installed app reads to learn about a newer version. bach build already writes it when your [updates] has github or a download_url. Use bach feed to write it again after signing, because signing changes the file and its SHA-256.

The feed

latest.json
  • version is read from the setup file’s manifest.
  • sha256 is computed from the file on disk, so run the command on the final, signed file.
  • size is the setup file’s size in bytes. The installed app uses it to check the disk has room before downloading.
  • rollout is only there with --rollout. Write the feed again without it to release to everybody.
  • delta is only there with a patch: { "from", "url", "sha256", "size" }. bach build --patch-from adds it by itself when the patch is at least a fifth smaller than the full file.
  • notes is left out when you do not pass --notes or --notes-file, and is cut at 4000 characters.

Errors

  • Without --url and without a bach.toml with an [updates] download link, the command asks for the https link.
  • A link that is not https is refused.
  • A file that is not a Bach setup file, or is an uninstaller, is refused with a sentence. So is an update patch given as FILE: pass the full setup file and the patch with --patch.
  • A --patch file that is not an update patch is refused.
See Updates.